Development Methodology - Revision history

Stephen K. Jolley at 17:20, 9 May 2014

2014-05-09T17:20:28Z

← Older revision		Revision as of 17:20, 9 May 2014
Line 3:		Line 3:
	* 1 week – planning and development week		* 1 week – planning and development week
	* 2-4 weeks – development		* 2-4 weeks – development
	* 1-3 week – stabilization		* 1-4 week – stabilization
	* 1 week – release		* 1 week – release

	(The above time adds up to more than 6-8 weeks due to the planning week overlapping the release week).		(The above time adds up to more than 5-8 weeks due to the planning week overlapping the release week).

	The final project milestone is 4-8 weeks of stabilization and release.		The final project milestone is up to 4 weeks of stabilization and then release.

	At the end of each milestone there is a milestone release that:		At the end of each milestone there is a milestone release that:

Stephen K. Jolley at 17:19, 9 May 2014

2014-05-09T17:19:40Z

← Older revision		Revision as of 17:19, 9 May 2014
Line 2:		Line 2:

	* 1 week – planning and development week		* 1 week – planning and development week
	* 4 weeks – development		* 2-4 weeks – development
	* 1-2 week – stabilization		* 1-3 week – stabilization
	* 1 week – release		* 1 week – release

Song at 12:39, 7 November 2011

2011-11-07T12:39:13Z

← Older revision		Revision as of 12:39, 7 November 2011
Line 1:		Line 1:
	The project will be managed as a series of 6-week milestones. The milestones will be broken out as follows:		The project will be managed as a series of 6-8-week milestones. The milestones will be broken out as follows:

	* 1 week – planning ~~for this milestone~~		* 1 week – planning and development week
	* 4 weeks – development		* 4 weeks – development
	* 1 week – stabilization		* 1-2 week – stabilization
	* 1 week – release		* 1 week – release

	(The above time adds up to more than 6 weeks due to the planning week overlapping the release week).		(The above time adds up to more than 6-8 weeks due to the planning week overlapping the release week).

	The final project milestone is 4 weeks of stabilization and release.		The final project milestone is 4-8 weeks of stabilization and release.

	At the end of each milestone there is a milestone release that:		At the end of each milestone there is a milestone release that:
Line 16:		Line 16:
	* can demonstrate some feature or features		* 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.		Each developer is expected to focus on 1-2 features/tasks at a time, which can help the team focus and also prevent from sending all pull requests at the end of a milestone. Project developers must respect this rule. It gives the maintainers a break.

Scottrifw at 14:44, 7 December 2010

2010-12-07T14:44:46Z

← Older revision		Revision as of 14:44, 7 December 2010
Line 6:		Line 6:
	* 1 week – release		* 1 week – release

	(The above adds up to more than 6 weeks~~, because in general,~~ the planning week ~~overlaps~~ the release week).		(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.		The final project milestone is 4 weeks of stabilization and release.

	At the end of each milestone is a milestone release~~, which has~~:		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 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 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.

Davest at 22:01, 6 December 2010

2010-12-06T22:01:15Z

← Older revision		Revision as of 22:01, 6 December 2010
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.

Davest: 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 * …'

2010-12-06T21:57:34Z

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 * …'

New page

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.

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.