Page History

...

• Release Coordinator: TBA - We still need volunteer(s) to act as Release Coordinator

Timeline and Proceeding

RELEASE TIMELINE IS NOT FINALIZED! Two Release Timelines have been proposed and are currently being decided upon by the Committers.

• Very Tentative Release Timeline (This should not be considered final)
  • June 3, 2011 : Beta 1 (Note: Open Repositories 2011 Conference is June 7-11)
  • July 8, 2011 : Beta 2
  • August 19, 2011 : Feature Freeze
  • August 26, 2011 : Final Documentation "Due Date"?
  • September 2, 2011 : Release Candidate 1
  • September 5-16, 2011 : Testathon
  • September 30, 2011 : Release Candidate 2
  • October 3-12, 2011 : Final Testing / Bug Fixing
  • October 14, 2011 : Final Releas

• A First a few definitions:
  • "Beta" Releases - These are a newly proposed idea for 1.8.0. Essentially a "Beta" release would be an very early release of the software, even before all features are finalized. They give developers an opportunity for early feedback from the community or other developers around a new features. They should not be considered stable (though hopefully they are relatively stable). Rather they are previews of upcoming features. Only features that are completed will be released into the Beta Release (i.e. the Beta Release waits for nothing – we release a new Beta even if there's not many new features completed). After and between Beta releases, features may change, up until the "Feature Freeze"
  • "Feature Freeze" - After this date, the feature listing cannot change. All new features must be completed by this date. After this date, the system is being stabilized in preparation for the first "Release Candidate"
  • "Release Candidate" releases - These are initial releases after all features have been finalized. Features may not change, but bug fixes can be made. They are meant for very broad testing (e.g. Testathon), in order to find & fix any last bugs before the Final Release.

• Proposed Release Timeline #1 - 9 months (same timeframe as 1.6.0 to 1.7.0)
  • May 13, 2011 : Beta 1
  • June 3, 2011 : Beta 2 (Note: OR11 is June 7-11)
  • July 22, 2011 : Feature Freeze
  • July 29, 2011 : Final Documentation "Due Date"?
  • August 5, 2011 : Release Candidate 1
  • August 8-19, 2011 : Testathon
  • September 2, 2011 : Release Candidate 2
  • September 5-14, 2011 : Final Testing / Bug Fixing
  • September 16, 2011 : Final Release

• Proposed Release Timeline #2 - 10 months (slightly longer timeframe, but if we moved to 12 months timeframe afterwards, then we'd just do a new release every October,
  • before the
  holidays get started)
  • June 3, 2011 : Beta 1 (Note: OR11 is June 7-11)
  • July 8, 2011 : Beta 2
  • August 19, 2011 : Feature Freeze
  • August 26, 2011 : Final Documentation "Due Date"?
  • September 2, 2011 : Release Candidate 1
  • September 5-16, 2011 : Testathon
  • September 30, 2011 : Release Candidate 2
  • October 3-12, 2011 : Final Testing / Bug Fixing
  • October 14, 2011 : Final Release
  Proposed Release Timeline #3 - 12-14 months (aimed to hopefully be released in time for submissions to OR 2012)
  • Dec, 2011 : Feature Freeze
  • Jan, 2012 : Testathon
  • First Quarter, 2012 : Final Release
  The main differences between these timelines are the following:
  • In Timeline #1, we release two "Beta" releases before OR11. Whereas, in Timeline #2, we just release one "Beta" before OR11. In Timeline #3, we are aiming for final release in time for OR12 submissions.
  • After this 1.8 release, several folks feel it might be good to move to a very consistent Release Schedule (e.g. every 12 months). If we went this route, then we would be "standardizing" on a release either, every September, every October, or the beginning of each year. If you feel one month is better than the other, that may be a deciding factor.

Release Process needs to proceed according to the following Maven release process: Release Procedure

...