Development Methodology: Difference between revisions
From Yocto Project
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
* 1 week – release | * 1 week – release | ||
(The above adds up to more than 6 weeks | (The above time adds up to more than 6 weeks due to the planning week overlapping the release week). | ||
The final project milestone is | The final project milestone is 4 weeks of stabilization and release. | ||
At the end of each milestone is a milestone release | At the end of each milestone there is a milestone release that: | ||
* been stabilized, with bugs tracked and showstoppers fixed | * has been stabilized, with bugs tracked and showstoppers fixed | ||
* has had some amount of QA beyond the nightly sanity test | * has had some amount of QA applied beyond the nightly sanity test | ||
* can demonstrate some feature or features | * can demonstrate some feature or features | ||
Milestones are divided | Milestones are divided into week-long "Sprints." This division prevents all of a milestone's functionality from hitting at the end of the milestone and causing a collision. Project developers must respect these divisions. it gives the maintainers a break. | ||
Revision as of 14:44, 7 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 time adds up to more than 6 weeks due to the planning week overlapping the release week).
The final project milestone is 4 weeks of stabilization and release.
At the end of each milestone there is a milestone release that:
- has been stabilized, with bugs tracked and showstoppers fixed
- has had some amount of QA applied beyond the nightly sanity test
- can demonstrate some feature or features
Milestones are divided into week-long "Sprints." This division prevents all of a milestone's functionality from hitting at the end of the milestone and causing a collision. Project developers must respect these divisions. it gives the maintainers a break.
