Versions Compared

Old Version 16

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 17

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Proposal for Committer Group Coordinated Release:

  • Since no one has volunteered as 1.7 Release Coordinator, we could

...

  • release 1.7.0 based on which features/fixes are ready & documented and have been deemed "acceptable" by the DSpace Committer Group.
  • In this way the DSpace Committers Group would act as the "Release Coordinators"
    • Additional "coordination" would happen amongst various ad-hoc "feature teams" (of interested developers). Those teams would have to work to meet the required schedule in order to get their proposed feature(s) into 1.7.0.
  • However, a lack of a single Release Coordinator may require us all to follow some 1.7 code committing "rules". These rules are here to keep us from stepping on each

...

  • others'

...

  • toes, and help us to stay on a tighter schedule.

Proposed 1.7 Code Committing Rules:

  1. No incomplete features in "Trunk", ever. If you are in-progress on a feature, create an SVN sandbox or module area to work on it, and pull it over to Trunk once it has been completed and is ready for testing & release.
  2. All new features must have documentation before committing to Trunk. If a feature has no documentation, it should not be committed to Trunk until there is some minimal documentation (minimal documentation includes documenting all configuration options).

Timeline and Proceeding

Proposed Release Timeline (all dates are tentative):

  • August 13, 2010 : Milestone 1 - "Feature Decision Day"
    • By this milestone, all major features or major architectural changes for 1.7.0 release should be approved by the DSpace Committers Group and be somewhere in SVN (they need not be fully finished, but should be moving along in their development process).
  • October 22, 2010 : Feature Freeze (all features must have initial documentation to be accepted)
    • All 1.7.0 features (major and minor) must be finished, committed to Trunk and have initial documentation. After this date, no new features will be accepted for the 1.7.0 release. Any features which are not finished or ready will need to be scheduled for the next DSpace release.
    • Modules which do not reside in Trunk (e.g. dspace-services) should also undergo a Feature Freeze on this date, so that we can work to stabilize all code used by out-of-the-box DSpace.
  • October 29, 2010 : Documentation "Soft Freeze"
    • All documentation changes need to be submitted.
  • November 5, 2010 : Release Candidate 1
  • November 8-12, 2010 : 1.7 Testathon Week
  • December 3, 2010 : Release Candidate 2 (if necessary), or Final Release
  • December 6-15, 2010 : Final Testing / Bug Fixing (if necessary)
  • December 17, 2010 : Final Release

...