| [p2-dev] Release schedule |
The platform team has announced the 3.5 planning which we will have to adhere to since significant parts of p2 are included.
Notice the early date for completion of any major feature work: 30 January that I like because it will make for a less hectic end of game.
M1 - August 8, 2008 (6 weeks)
focus on critical issues to backport to 3.4.1
experimental work
>>> (3.4.1/Ganymede-SR1 +0 dates: RC1-September 1, RC2-September 8, RC3-September 15)
M2 - September 19, 2008 (6 weeks) - PLANNING
all teams have their release dev plan fleshed out, with proper staging of feature work (per milestone)
all teams have assess their performance status: reviewed their performance results *and* identified areas for improvements, and planned major perf work (which is too big for addressing late in M7)
all teams have reviewed their documentation state, and planned actions for it
all teams have posted their smoke test plans, and assessed their level of test coverage (and planned for reducing addressing gaps)
M3 - October 31, 2008 (6 weeks) - DEV
graduation plans for components from incubators are defined, paperwork/CQ etc initiated with foundation
test coverage items actionned, automated builds provide test coverage assessment
M4 - December 12, 2008 (6 weeks) - DEV
focus on critical issues to backport to 3.4.2
M5 - January 30, 2009 (7 weeks) - MAJOR FEATURE WORK COMPLETED
>>> (3.4.2/Ganymede-SR2 +0 dates: RC1-February 2, RC2-February 9, RC3-February 16)
M6 - March 13, 2009 (6 weeks) - API FREEZE, FEATURE TUNING, I18N & ACCESSIBILITY
>>> (EclipseCon March 23-27)
M7 - May 1st, 2009 (7 weeks) - PERFORMANCE & POLISH, BEST EFFORT ON DOC
all tests must be green or accounted properly (still failure)
polish effort carried by dynamic team
RC1 (2 weeks) - May 15, 2009
RC2 (1 week) - May 22, 2009
RC3 (1 week) - May 29, 2009
RC4 (1 week) - June 5, 2009
PaScaL