Actions

Difference between revisions of "Joomla! Maintenance Procedures"

From Joomla! Documentation

Line 5: Line 5:
 
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.
 
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.
  
[[Image:Joomla!+Bug+Tracking+Process.tiff]]
+
<image goes here>
 +
 
 +
 
 +
 
 +
== Reporting issues ==
 +
 
 +
The process is started in one of two ways: the bug is added to the tracker, or a user reports the bug in the Quality and Testing forum for the given major/minor release.
 +
 
 +
** Reported on the forums. If a bug is reported on the forums is the Quality and Testing
 +
Working Group's responsibility to verify the bug and add it to the forge tracker. The
 +
Quality and Testing Member who evaluates the bug should modify the thread on the forum
 +
according to what action was taken.
 +
** Invalid. If the report was determined to either not be a bug or a known issue this should
 +
be reflected in the thread.
 +
** Valid. If the report was verified as a bug and was added to the tracker the forum thread
 +
should reflect that as well as have a link added to the tracker artifact.
 +
 
 +
== Resolving issues ==
 +
 
 +
== Report resolved issues ==
 +
 
 +
== Verify the results ==

Revision as of 15:59, 15 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.

People will notice that the content of this document look a lot like the former Quality and Testing. That is absolutely true because the main discussion here is that we talk on 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, 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 following flowchart provides a very rough description of how the issue tracking process is defined.

<image goes here>


Contents

Reporting issues

The process is started in one of two ways: the bug is added to the tracker, or a user reports the bug in the Quality and Testing forum for the given major/minor release.

    • Reported on the forums. If a bug is reported on the forums is the Quality and Testing

Working Group's responsibility to verify the bug and add it to the forge tracker. The Quality and Testing Member who evaluates the bug should modify the thread on the forum according to what action was taken.

    • Invalid. If the report was determined to either not be a bug or a known issue this should

be reflected in the thread.

    • Valid. If the report was verified as a bug and was added to the tracker the forum thread

should reflect that as well as have a link added to the tracker artifact.

Resolving issues

Report resolved issues

Verify the results