Development Cycle - Revision history

Tom Hutchison: added Category:Joomla! Resources using HotCat

2013-11-30T16:38:18Z

added Category:Joomla! Resources using HotCat

← Older revision		Revision as of 16:38, 30 November 2013
Line 33:		Line 33:
	Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.		Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.
	<noinclude> </noinclude>		<noinclude> </noinclude>

			[[Category:Joomla! Resources]]

Tom Hutchison: removed Category:Working Groups using HotCat

2013-11-30T16:38:01Z

removed Category:Working Groups using HotCat

← Older revision		Revision as of 16:38, 30 November 2013
Line 33:		Line 33:
	Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.		Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.
	<noinclude> </noinclude>		<noinclude> </noinclude>
	~~[[Category:Working Groups]]~~

Tom Hutchison: removed Category:Bug Squad using HotCat

2013-11-30T16:37:57Z

removed Category:Bug Squad using HotCat

← Older revision		Revision as of 16:37, 30 November 2013
Line 32:		Line 32:

	Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.		Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.
	<noinclude> ~~[[Category:Bug Squad]]~~</noinclude>		<noinclude> </noinclude>
	[[Category:Working Groups]]		[[Category:Working Groups]]

Tom Hutchison: removed Category:Development Working Group using HotCat

2013-11-30T16:37:46Z

removed Category:Development Working Group using HotCat

← Older revision		Revision as of 16:37, 30 November 2013
Line 32:		Line 32:

	Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.		Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.
	<noinclude>~~[[Category:Development Working Group]]~~[[Category:Bug Squad]]</noinclude>		<noinclude> [[Category:Bug Squad]]</noinclude>
	[[Category:Working Groups]]		[[Category:Working Groups]]

Batch1211 at 13:11, 20 September 2010

2010-09-20T13:11:08Z

← Older revision		Revision as of 13:11, 20 September 2010
Line 33:		Line 33:
	Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.		Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.
	<noinclude>[[Category:Development Working Group]][[Category:Bug Squad]]</noinclude>		<noinclude>[[Category:Development Working Group]][[Category:Bug Squad]]</noinclude>
			[[Category:Working Groups]]

Chris Davenport: Categorisation.

2008-11-03T18:31:33Z

Categorisation.

← Older revision		Revision as of 18:31, 3 November 2008
Line 1:		Line 1:
	~~[[Category:Development]]~~
	~~[[Category:Bug Squad]]~~
	[[Image:montano_wheel.png\|right]]We have adopted a three phase development cycle. The three phases are:		[[Image:montano_wheel.png\|right]]We have adopted a three phase development cycle. The three phases are:

Line 34:		Line 32:

	Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.		Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.
			<noinclude>[[Category:Development Working Group]][[Category:Bug Squad]]</noinclude>

Masterchief at 07:02, 4 September 2008

2008-09-04T07:02:13Z

← Older revision		Revision as of 07:02, 4 September 2008
Line 1:		Line 1:
			[[Category:Development]]
			[[Category:Bug Squad]]
	[[Image:montano_wheel.png\|right]]We have adopted a three phase development cycle. The three phases are:		[[Image:montano_wheel.png\|right]]We have adopted a three phase development cycle. The three phases are:

Line 32:		Line 34:

	Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.		Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.

	~~[[Category:Development]]~~

Willebil at 13:41, 15 March 2008

2008-03-15T13:41:31Z

← Older revision		Revision as of 13:41, 15 March 2008
Line 8:		Line 8:

	These three phases are also known as the Opening, Mid-Game and End Game among project managers. As you can see each phase has a different main focus, focus in the Alpha phase is on Development but shifts to Documentation and Testing for the Beta phase and finally to Public Information in the Stable phase.		These three phases are also known as the Opening, Mid-Game and End Game among project managers. As you can see each phase has a different main focus, focus in the Alpha phase is on Development but shifts to Documentation and Testing for the Beta phase and finally to Public Information in the Stable phase.


	== Alpha Phase ==		== Alpha Phase ==

CirTap: /* Stable Phase */

2008-02-12T12:03:26Z

Stable Phase

← Older revision		Revision as of 12:03, 12 February 2008
Line 32:		Line 32:
	During the stable phase we release one or more release candidates. At this phase code base is considered stable and secure and any final bugs are taken care of as they come to our attention. It is during this phase of the development cycle that the software is packaged and released. Most attention goes into promotion and public information.		During the stable phase we release one or more release candidates. At this phase code base is considered stable and secure and any final bugs are taken care of as they come to our attention. It is during this phase of the development cycle that the software is packaged and released. Most attention goes into promotion and public information.

	Control over the code base from the release is delegated from the [[Development ~~team~~]] to the [[Bug Squad]. During this stage the [[Joomla! Maintenance Procedures]] are in place.		Control over the code base from the release is delegated from the [[Development Team]] to the [[Bug Squad]]. During this stage the [[Joomla! Maintenance Procedures]] are in place.

	[[Category:Development]]		[[Category:Development]]

Masterchief: Revisions due to introduction of white paper policy

2008-02-07T23:10:20Z

Revisions due to introduction of white paper policy

← Older revision		Revision as of 23:10, 7 February 2008
Line 11:		Line 11:

	== Alpha Phase ==		== Alpha Phase ==
	The Alpha phase of the development cycle is when we ~~implement~~ the ~~features outlined in~~ the ~~roadmap and perform any necessary refactoring~~. ~~Community input~~ is ~~minimal and restricted. The system can break for~~ the ~~new features we are implementing but care should be taken that other refractory achieves backwards compatibility rate as defined in~~ the ~~code base life cycle. At this phase anything in the source tree can~~ and ~~likely will change as we search for the best methods of achieving our development goals. Most system testing~~ is done by the ~~developers themselves as they come across issues related to~~ the ~~framework changes~~.		The Alpha phase of the development cycle is when we decide on what the goals are for the next release. This is by far the most important part of the process and is done in complete consultation with the community through the submission of public [[White Papers]]. The acceptance of papers sets the functional requirements for all the goals in the release.

	~~This stage is~~ for ~~refactoring core extensions and for making user interface tweaks. With a more robust and extendable API in place, we should be able to remove redundant code and improve performance~~ in the ~~core components. For these reasons there can me multiple Alpha versions~~.

	By working closely with third party developers ~~and keeping lines of communication open~~ as we transition from the Alpha to the Beta phase we hope to be able to provide all necessary information and support to ensure that their extensions are compatible with future versions of Joomla!		This is a time for fixing more complex issues that have arisen from the previous version, for implementing new features and functionality, and for dropping parts of the code that have been previously earmarked for removal, or deemed to be no longer necessary.

			During this time the development trunk will be in a state of flux and break from time to time. Several Alpha releases may be made to allow the user and third-party developer community to comment on the progress of the work in terms of the goals set.

			By working closely with third party developers as we transition from the Alpha to the Beta phase we hope to be able to provide all necessary information and support to ensure that their extensions are compatible with future versions of Joomla!

	== Beta Phase ==		== Beta Phase ==