Hello from the DSpace 3.0 Release Team!
We've been discussing a number of things that are unique to this release and
we'd like to suggest some adjustments that will hopefully make the process
smoother.
Particularly unique to this release is the fact that this is the first time
GitHub has been in place as our code management system. This has impacted the
workflow of accepting contributions and how they make their way into the final
release. Because of this, we believe the release process could be better
aligned with the new workflow. Pursuant of that, we would like to announce the
following changes:
1.) What we have been calling the "Feature Freeze" date will now be referred
to as the "Code Submission Deadline". This helps to clarify exactly what is
needed by this date. Due to the fact that we now receive Git Pull
Requests<https://help.github.com/articles/using-pull-requests/>, the
contributor can continue to refine and shape their submission, even after
offering the code for contribution, often as part of a dialog with the
committers. The Code Submission Deadline makes clear that Pull Requests for
working code intended for a release are due by this date, not that the code
need be reviewed, discussed, documented and fully merged with the codebase to
be included in the release. Any new feature code submitted after this date
will NOT be in 3.0 & will not even be reviewed for the current release
(obviously the only exception is bug fixes).
2.) The name "Feature Freeze" will now refer to the date by which the Release
Team and Committers will have reviewed via Pull Request, and accepted or
rejected all contributions made for a certain release. Rejected code has to
wait for the next version of DSpace (or is suggested to be released separate
from the current release as a "third party add-on", if applicable).
3.) Regarding the current release, we would like to adjust the timeline to
allow for a more thorough review of the numerous contributions being considered
for 3.0. Below is an outline of the new schedule:
- Aug 24 : Feature/Code Submission Deadline
- Aug 31 : Feature Documentation Due Date
- Sept 7 : Feature Freeze
- Sept 14 : Release Candidate 1 is released
- Sept 17-28 : Test-a-thon
- Oct 12 : Release Candidate 2 is released
- Oct 15-24 : Final Testing & Bug Fixing period
- Oct 26 : 3.0 is released
We hope these changes will make for an easier and more clear release process.
- Sands Fish, for the DSpace 3.0 Release Team
P.S. - Many thanks go to Tim Donohue & Valorie Hollister for their consultation
and input into this decision.
--
sands fish
Senior Software Engineer
MIT Libraries
Technology Research & Development
[email protected]<mailto:[email protected]>
E25-131
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
