Re: [OpenDaylight Discuss] release planning for Helium
Ed Warnicke (eaw) <eaw@...>
These dates seem a bit aggressive, especially given that we are positing an opening date
toggle quoted message
Show quoted text
that is before the time it could be decided :) I would suggest the following: M0 - 5/5 M1 - 6/2 - Last day to join, publish release plans M2 - 6/30 - Finalize release plans M3 - 7/28 - Last call for CI (what does last call for CI mean?) M4 - 8/25 - API Freeze M5 - 9/29 - Code freeze RC0 - 10/6 RC1 - 10/13 RC2 - 10/20 Final - 10/27 This allows reasonable time for new projects to get through the creation review process and join the release, as well as allowing adequate time for projects to plan and cooperate. Ed On Mar 25, 2014, at 12:55 PM, Chris Wright <chrisw@...> wrote:
As nice as it is to bask in the glory of the afterglow...it's time to |
|