Actions

Difference between revisions of "Joomla! Maintenance Procedures"

From Joomla! Documentation

Line 1: Line 1:
 
Once a major/minor release has reached the [[Stable phase]] in the [[Development Cycle]] the processes and procedures for development change. The most immediate thing to notice is that the development is no longer driven by the [[Development team]] when the [[Stable phase]] is reached. As soon as the major/minor release is declared stable all future development on that release is driven by the [[Bug Squad]]. It is important to understand the way we think about [[Maintenance releases]] because one of the things that our community depends upon is stability. Stability is born of a rigorous testing process and accountability. This document will outline the procedures and processes for maintaining a Joomla! major/minor release.
 
Once a major/minor release has reached the [[Stable phase]] in the [[Development Cycle]] the processes and procedures for development change. The most immediate thing to notice is that the development is no longer driven by the [[Development team]] when the [[Stable phase]] is reached. As soon as the major/minor release is declared stable all future development on that release is driven by the [[Bug Squad]]. It is important to understand the way we think about [[Maintenance releases]] because one of the things that our community depends upon is stability. Stability is born of a rigorous testing process and accountability. This document will outline the procedures and processes for maintaining a Joomla! major/minor release.
  
People will notice that the content of this document look a lot like a description of the former Quality and Testing team. That is absolutely true because the main discussion here is about the Quality processes for Joomla! The main difference is the way the [[Bug Squad]] is organised compared to the former Quality and Testing team, but they strive to reach the same goals.  
+
Once a release has been declared stable ([[Maintenance Release]]), all bugs and artifacts are to be tracked in our official [[Tracker]] on the Joomla! GForge site: [[http://www.joomlacode.org]]. Having a single place for confirmed issue tracking provides us all with a simple system of accountability.  
  
Once a release has been declared stable, all bugs and artifacts are to be tracked in our official tracker on the Joomla! GForge site: [[http://www.joomlacode.org]]. Having a single place for confirmed issue tracking provides us all with a simple system of accountability. The following flowchart provides a very rough description of how the issue tracking process is defined.
+
The maintenance procedures have the following stages :
 +
* [[Reporting issues]]; We keep track on the open issues in our [[Tracker]] but issues can be reported in two ways; from the forum or directly into the tracker. An description of the process of [Reporting issues]] is available (click the link).
 +
* [[Resolving issues]]; Once a issue is confirmed there are several ways an issues can get solved. First members from the [[Development team]] can work on solving the issue, but also community members can send in patches. The general way of working is: create patch, test patch, commit patch. A description of the [[Resolving issues]] process is available (click the link).
  
The bug handling process has three stages in general:
+
The maintenance procedures implement the Quality processes for Joomla! This process differs only during development stage of a [[Major release]] or a [[Minor release]] for the [[Resolving issues]] process. In maintenance releases we work with patches, and within the [[Development cycle]] of a [[Major release]] or a [[Minor release]] developers will fix issues directly in the trunk until the codebase goes to a stage of [[Release Candidate]].
* [[Reporting issues]]
+
* [[Resolving issues]]
+
* [[Verifying the results]]
+
  
 +
 +
----- keep link below, is current archive --
  
 
[[dummy ]]
 
[[dummy ]]

Revision as of 11:10, 30 January 2008

Once a major/minor release has reached the Stable phase in the Development Cycle the processes and procedures for development change. The most immediate thing to notice is that the development is no longer driven by the Development team when the Stable phase is reached. As soon as the major/minor release is declared stable all future development on that release is driven by the Bug Squad. It is important to understand the way we think about Maintenance releases because one of the things that our community depends upon is stability. Stability is born of a rigorous testing process and accountability. This document will outline the procedures and processes for maintaining a Joomla! major/minor release.

Once a release has been declared stable (Maintenance Release), all bugs and artifacts are to be tracked in our official Tracker on the Joomla! GForge site: [[1]]. Having a single place for confirmed issue tracking provides us all with a simple system of accountability.

The maintenance procedures have the following stages :

  • Reporting issues; We keep track on the open issues in our Tracker but issues can be reported in two ways; from the forum or directly into the tracker. An description of the process of [Reporting issues]] is available (click the link).
  • Resolving issues; Once a issue is confirmed there are several ways an issues can get solved. First members from the Development team can work on solving the issue, but also community members can send in patches. The general way of working is: create patch, test patch, commit patch. A description of the Resolving issues process is available (click the link).

The maintenance procedures implement the Quality processes for Joomla! This process differs only during development stage of a Major release or a Minor release for the Resolving issues process. In maintenance releases we work with patches, and within the Development cycle of a Major release or a Minor release developers will fix issues directly in the trunk until the codebase goes to a stage of Release Candidate.



keep link below, is current archive --

dummy