Development Methodology: Difference between revisions
From Yocto Project
Jump to navigationJump to search
(Created page with 'The project will be managed as a series of 6-week milestones. The milestones will be broken out as follows: * 1 week – planning for this milestone * 4 weeks – development * …') |
No edit summary |
||
| Line 9: | Line 9: | ||
The final project milestone is: 4 weeks of stabilization and release. | The final project milestone is: 4 weeks of stabilization and release. | ||
At the end of each milestone is a milestone release, which has: | |||
* been stabilized, with bugs tracked and showstoppers fixed | |||
* has had some amount of QA beyond the nightly sanity test | |||
* can demonstrate some feature or features | |||
Milestones are divided up into week-long "Sprints" to prevent all of a milestone's functionality from hitting at the end of the milestone and causing a collision. Project developers must respect this, to give a break to the maintainers. | Milestones are divided up into week-long "Sprints" to prevent all of a milestone's functionality from hitting at the end of the milestone and causing a collision. Project developers must respect this, to give a break to the maintainers. | ||
Revision as of 22:01, 6 December 2010
The project will be managed as a series of 6-week milestones. The milestones will be broken out as follows:
- 1 week – planning for this milestone
- 4 weeks – development
- 1 week – stabilization
- 1 week – release
(The above adds up to more than 6 weeks, because in general, the planning week overlaps the release week).
The final project milestone is: 4 weeks of stabilization and release.
At the end of each milestone is a milestone release, which has:
- been stabilized, with bugs tracked and showstoppers fixed
- has had some amount of QA beyond the nightly sanity test
- can demonstrate some feature or features
Milestones are divided up into week-long "Sprints" to prevent all of a milestone's functionality from hitting at the end of the milestone and causing a collision. Project developers must respect this, to give a break to the maintainers.
