[Portfolio] OSP Independent Release
hbzhang at vt.edu
Mon Jul 19 20:57:27 PDT 2010
I think the independent release of OSP can be a very nice idea. It will
facilitate the progress of OSP development in the very long run. It also
helps to more efficiently integrate OSP to Sakai 3.0.
The only trade off is to stay being both independent and harmony with Sakai
This brings the future OPS development plan issue. It is to reduce the
dependency of OPS on other Sakai modules (widgets), while providing
excellent support to other Sakai Widgets.
From: portfolio-bounces at collab.sakaiproject.org
[mailto:portfolio-bounces at collab.sakaiproject.org] On Behalf Of Beth
Sent: Monday, July 19, 2010 5:09 PM
To: Anthony Whyte
Cc: osp List
Subject: [Portfolio] OSP Independent Release
On today's OSP conference call, we decided to go ahead with OSP
independent releases, and wanted to ask your help going forward.
Here's an overview of our plan -- feel free to contact me off-list for
specific nuts-and-bolts questions as appropriate:
1) The OSP releases will continue the current enumeration pattern
(e.g. the next release will be 2.8, followed by 2.9, with optional
iterations in between, such as 2.8.1).
2) The OSP release cycle will be based on functional availability,
with the next (OSP 2.8) release based on the current trunk build, and
the OSP 2.9 release based on some new features that Indiana is
developing: Roster Synchronization (SAK-16693) and Email Preferences
3) There are at least two dependencies that we are aware of: Metaobj
4) There were also some questions regarding the continuous build
server that you are working on (e.g. who should have access, what is
the process for updating, etc.).
5) We would like to take you up on your offer to help with the
repackaging of the OSP pom.xml files in preparation for an independent
portfolio mailing list
portfolio at collab.sakaiproject.org
TO UNSUBSCRIBE: send email to portfolio-unsubscribe at collab.sakaiproject.org
with a subject of "unsubscribe"
More information about the portfolio