Bug Tracking Process - Revision history

Unworthyslave: /* Resolving Issues */

2012-12-27T01:29:16Z

‎Resolving Issues

Unworthyslave: /* Resolving Issues */

2012-12-27T01:28:50Z

‎Resolving Issues

Unworthyslave: /* Resolving Issues */

2012-12-27T01:26:28Z

‎Resolving Issues

Unworthyslave: /* Resolving Issues */

2012-12-27T01:25:19Z

‎Resolving Issues

Unworthyslave: /* Resolving Issues */

2012-12-27T01:24:58Z

‎Resolving Issues

Dextercowley: fix some typos and clarify

2012-09-09T14:55:57Z

fix some typos and clarify

Dextercowley: /* Overview */

2012-09-09T14:52:56Z

‎Overview

Unworthyslave at 20:47, 8 September 2012

2012-09-08T20:47:54Z

Hutchy68: update image links to png

2012-09-07T05:23:50Z

update image links to png

Radiant tech: edited url for bug tracker to location for 1.6+

2011-10-28T18:58:08Z

edited url for bug tracker to location for 1.6+

@@ Line 59: / Line 59: @@
 * '''Information Required''' is used if we need more information ''from the person who reported the issue'' to decide about the issue. For example, there are questions about how to reproduce the problem or other questions about the issue. If we get the information we need, then we can continue processing the issue. If we don't get the information within two weeks, then we can change the status to Unable to confirm (or another of the closed status codes if that is more applicable).
 * '''Needs Review''' is used if we need a JBS Coordinator, Development Coordinator, or other experienced developer to review the issue. This is different from Information Required, which means that we need more information from the person who reported the issue.
-* '''Started''' means that JBS has checked the issue, but is not quite sure if the issue is an actual bug (i.e. confirmed), and that there is discussion going on about the issue, which doesn't require additional information ''from the person who reported the issue.  It is a state that's between '''Opened''' and '''Confirmed'''.
+* '''Started''' means that JBS has checked the issue, but is not quite sure if the issue is an actual bug (i.e. confirmed), and that there is discussion going on about the issue, which doesn't require additional information ''from the person who reported the issue''.  It is a state that's between '''Opened''' and '''Confirmed'''.
 * '''Confirmed''' means that JBS has confirmed that this issue is a bug in Joomla! that should be fixed. That's when the JBS tries to solve it or consults with the development team about a solution. ''At this point there should be clear step-by-step test instructions that indicate how to reproduce the problem. For version 1.6, use the Test Instructions field for this information.''
 * '''Pending''' means that a patch has been submitted that a JBS member or development coordinator or appropriate leadership team member believes fixes the bug. If needed, additional test instructions are entered for the issue. Every Pending issue should have instructions that tell the tester how to reproduce the problem and make sure the patch fixes the problem.

@@ Line 59: / Line 59: @@
 * '''Information Required''' is used if we need more information ''from the person who reported the issue'' to decide about the issue. For example, there are questions about how to reproduce the problem or other questions about the issue. If we get the information we need, then we can continue processing the issue. If we don't get the information within two weeks, then we can change the status to Unable to confirm (or another of the closed status codes if that is more applicable).
 * '''Needs Review''' is used if we need a JBS Coordinator, Development Coordinator, or other experienced developer to review the issue. This is different from Information Required, which means that we need more information from the person who reported the issue.
-* '''Started''' means that JBS has checked the issue, but is not quite sure if the issue is an actual bug (i.e. confirmed), and that there is discussion going on about the issue, which doesn't require additional information ''from the person who reported the issue.
+* '''Started''' means that JBS has checked the issue, but is not quite sure if the issue is an actual bug (i.e. confirmed), and that there is discussion going on about the issue, which doesn't require additional information ''from the person who reported the issue.  It is a state that's between '''Opened''' and '''Confirmed'''.
 * '''Confirmed''' means that JBS has confirmed that this issue is a bug in Joomla! that should be fixed. That's when the JBS tries to solve it or consults with the development team about a solution. ''At this point there should be clear step-by-step test instructions that indicate how to reproduce the problem. For version 1.6, use the Test Instructions field for this information.''
 * '''Pending''' means that a patch has been submitted that a JBS member or development coordinator or appropriate leadership team member believes fixes the bug. If needed, additional test instructions are entered for the issue. Every Pending issue should have instructions that tell the tester how to reproduce the problem and make sure the patch fixes the problem.

@@ Line 59: / Line 59: @@
 * '''Information Required''' is used if we need more information ''from the person who reported the issue'' to decide about the issue. For example, there are questions about how to reproduce the problem or other questions about the issue. If we get the information we need, then we can continue processing the issue. If we don't get the information within two weeks, then we can change the status to Unable to confirm (or another of the closed status codes if that is more applicable).
 * '''Needs Review''' is used if we need a JBS Coordinator, Development Coordinator, or other experienced developer to review the issue. This is different from Information Required, which means that we need more information from the person who reported the issue.
-* '''Started''' means that JBS has checked the issue, but is not quite sure if the issue is an actual bug (i.e. confirmed), and that there is discussion going on about the issue, which doesn't require additional information ''from the person who reported the issue'.
+* '''Started''' means that JBS has checked the issue, but is not quite sure if the issue is an actual bug (i.e. confirmed), and that there is discussion going on about the issue, which doesn't require additional information ''from the person who reported the issue.
 * '''Confirmed''' means that JBS has confirmed that this issue is a bug in Joomla! that should be fixed. That's when the JBS tries to solve it or consults with the development team about a solution. ''At this point there should be clear step-by-step test instructions that indicate how to reproduce the problem. For version 1.6, use the Test Instructions field for this information.''
 * '''Pending''' means that a patch has been submitted that a JBS member or development coordinator or appropriate leadership team member believes fixes the bug. If needed, additional test instructions are entered for the issue. Every Pending issue should have instructions that tell the tester how to reproduce the problem and make sure the patch fixes the problem.

@@ Line 59: / Line 59: @@
 * '''Information Required''' is used if we need more information ''from the person who reported the issue'' to decide about the issue. For example, there are questions about how to reproduce the problem or other questions about the issue. If we get the information we need, then we can continue processing the issue. If we don't get the information within two weeks, then we can change the status to Unable to confirm (or another of the closed status codes if that is more applicable).
 * '''Needs Review''' is used if we need a JBS Coordinator, Development Coordinator, or other experienced developer to review the issue. This is different from Information Required, which means that we need more information from the person who reported the issue.
-* '''Started'' means that JBS has checked the issue, but is not quite sure if the issue is an actual bug (i.e. confirmed), and that there is discussion going on about the issue, which doesn't require additional information ''from the person who reported the issue'.
+* '''Started''' means that JBS has checked the issue, but is not quite sure if the issue is an actual bug (i.e. confirmed), and that there is discussion going on about the issue, which doesn't require additional information ''from the person who reported the issue'.
 * '''Confirmed''' means that JBS has confirmed that this issue is a bug in Joomla! that should be fixed. That's when the JBS tries to solve it or consults with the development team about a solution. ''At this point there should be clear step-by-step test instructions that indicate how to reproduce the problem. For version 1.6, use the Test Instructions field for this information.''
 * '''Pending''' means that a patch has been submitted that a JBS member or development coordinator or appropriate leadership team member believes fixes the bug. If needed, additional test instructions are entered for the issue. Every Pending issue should have instructions that tell the tester how to reproduce the problem and make sure the patch fixes the problem.

@@ Line 59: / Line 59: @@
 * '''Information Required''' is used if we need more information ''from the person who reported the issue'' to decide about the issue. For example, there are questions about how to reproduce the problem or other questions about the issue. If we get the information we need, then we can continue processing the issue. If we don't get the information within two weeks, then we can change the status to Unable to confirm (or another of the closed status codes if that is more applicable).
 * '''Needs Review''' is used if we need a JBS Coordinator, Development Coordinator, or other experienced developer to review the issue. This is different from Information Required, which means that we need more information from the person who reported the issue.
-* '''Confirmed''' means that JBS has confirmed that this issue is a bug in Joomla! that should be fixed. That's when the JBS tries to solve it or consults with the development team about a solution. ''At this point there should be clear step-by-step test instructions that indicate how to reproduce the problem. For version 1.6, use the Test Instructions field for this information.''
+* '''Started'' means that JBS has checked the issue, but is not quite sure if the issue is an actual bug (i.e. confirmed), and that there is discussion going on about the issue, which doesn't require additional information ''from the person who reported the issue'.
 * '''Pending''' means that a patch has been submitted that a JBS member or development coordinator or appropriate leadership team member believes fixes the bug. If needed, additional test instructions are entered for the issue. Every Pending issue should have instructions that tell the tester how to reproduce the problem and make sure the patch fixes the problem.
 * '''In Progress''' means that an issue is being worked on. This will most likely be a situation where the issue was set to Pending but there were problems with the patch that require additional work. It also may be a case where the issue is complex and will take some time to solve. JBS members can participate in In Progress issues but generally should not start coding before discussing with others working on the issue already.

@@ Line 3: / Line 3: @@
 Joomla! bugs are tracked in the follower trackers:
-*[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 Joomla! CMS Issue Tracker] - Active
+*[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 Joomla! CMS Issue Tracker] - Active. This is for issues that affect version 3.0 and later.
-*[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=11410 Joomla! 2.5 Bug Tracker] - Active - this is for issues that *only* affect 2.5.  For issues that affect 2.5 and 3.0, please put them in the Joomla! CMS Issue Tracker (see above).
+*[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=11410 Joomla! 2.5 Bug Tracker] - Active. This is for issues that *only* affect version 2.5.  For issues that affect 3.0 and later, use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 Joomla! CMS Issue Tracker] (see above).
-*[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=32 Joomla! 1.5 Bug Tracker] - Active - this is for issues that *only* affect 1.5.  For issues that affect 2.5 and 3.0, please put them in the Joomla! CMS Issue Tracker (see above).
+*[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=32 Joomla! 1.5 Bug Tracker] - Active. This is for issues that *only* affect 1.5.  For issues that affect 2.5 and 3.0, use the trackers above. Note that version 1.5 is no longer under active development.
 *[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=5782 Joomla! 1.0 Bug Tracker] - Closed

@@ Line 1: / Line 1: @@
 =Overview=
-The [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 Joomla! Bug Tracker] is the place where all Joomla! bugs are tracked. This article documents the current Joomla! bug tracking process from the time a new bug is reported to the time it is closed.  ([http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=32 Joomla! 1.5 Bug Tracker])
+This article documents the current Joomla! bug tracking process from the time a new bug is reported to the time it is closed.
 =Reporting Issues=
@@ Line 6: / Line 12: @@
 [[Image:ReportingIssues.png|1024px]]
-The process is normally started in one of two ways: the bug is added to the tracker, or a user reports the bug in the [http://forum.joomla.org/viewforum.php?f=199 Joomla! Bug Forum] for the given maintenance release.
+The process is normally started in one of two ways: the bug is added to the respective tracker, or a user reports the bug in the [http://forum.joomla.org/viewforum.php?f=199 Joomla! Bug Forum] for the given maintenance release.
 == Issues reported on the forum ==
@@ Line 41: / Line 47: @@
 = Resolving Issues =
-The bug squad takes care of the 1.5 release which is now in maintenance mode. That means getting the 1.5.1, 1.5.2, 1.5.3, 1.5.4  etc releases ready by fixing problems that come up. The idea is to make the release increasingly stable and take care of issues that come up. At the same time, it is vitally important not to break anything that is working. That's called software regression and it's not something you want at this stage.
+The bug squad takes care of the Joomla releases. For example, that means getting the 3.0.1, 3.0.2, 3.0.3, 3.0.4  etc releases ready by fixing problems that come up. The idea is to make the release increasingly stable and take care of issues that come up. At the same time, it is vitally important not to break anything that is working. That's called software regression and it's not something you want at this stage.
-In the 1.5 tracker there are several common statuses, mainly: open, confirmed, pending, ready to commit.
+In the trackers there are several common statuses, mainly: open, confirmed, pending, ready to commit.
 * '''Open''' means it's reported, but it hasn't been determined for sure whether it is a real bug or not. Many Open issues are not actually bugs. If the issue fits into one of the categories below, then the status is changed as indicated and the bug is closed:

@@ Line 4: / Line 4: @@
 =Reporting Issues=
-[[Image:ReportingIssues.jpg|1024 px]]
+[[Image:ReportingIssues.png|1024px]]
 The process is normally started in one of two ways: the bug is added to the tracker, or a user reports the bug in the [http://forum.joomla.org/viewforum.php?f=199 Joomla! Bug Forum] for the given maintenance release.
@@ Line 61: / Line 61: @@
 The flowchart below provides a visual guide to how the process for resolving bugs works.
-[[Image:ResolvingIssues.jpg|1024 px]]
+[[Image:ResolvingIssues.png|800px]]
 You do ''not'' need to be a member of the JBS to help fix bugs in Joomla. Anyone can report bugs, test patches, or submit patches. If you want to help with resolving bugs, go to the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=32 Tracker]. You can help resolve Open issues as outlined above. You can create and submit patches for Confirmed issues. Or you can help test Pending issues. To report about what you have done, login to joomlacode and add a comment. You'll be amazed at how much impact you can have and how good it feels to contribute to the Joomla! project.