Year 2008 planning

Please find here the year 2008 suggested planning as late as 2007 December. We now propose static time frames (“sprint” in Scrum vocabulary): we suffered too much of huge releases qualification and profiling on past (1.3, 1.4) releases. We now want smaller releases and predictable release dates. It's one of the main agile methods principles; we hope it will make the year 2008 smoother.

V	Codename	Development	Finishing	Qualification	Release	Stabilisation
1.5	Lothlorien (released)	Weeks 46 (2007) to week 02 (2008)	Week 03	Weeks 04 & 05	2008/02/03	Weeks 06 & 07
1.6	Summertime	Weeks 08 to 16	Week 17	Weeks 18 & 19	2008/05/11	Weeks 20 & 21
1.7	Firestarter	To be scheduled	To be scheduled	To be scheduled	To be scheduled	To be scheduled
1.8	Breathless	To be scheduled	To be scheduled	To be scheduled	To be scheduled	To be scheduled

Phases details

• Development time frame is 8 weeks long
• Finishing phase contains:
  • The new features profiling (done by devs, can be done with VisualVM profiler for ie)
  • The test cases creation in the Jajuk Quality Center (currently done by devs, help is welcomed)
  • The documentation updates (currently done by devs, doc writers are welcomed)
  • The translations updates (done by translators)
• Qualification is planned to be done over only 2 weeks and is done through the Jajuk Quality Center
• Stabilization is dedicated to bug fixing on recently released version and to a bit of REST for members ;-)