Actions

Difference between revisions of "Bug Squad"

From Joomla! Documentation

(team leader update)
m (added category)
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Image:workgroups_bugsquad.jpg|right]]
+
<div style="background-color:#FFFFC2; margin:0; padding:8px 8px; border:1px solid #aaccff">
 
+
<!-- This portal was created using subst:box portal skeleton  -->
The Joomla! Bug Squad (JBS) is a team within the production working group. Their job is to identify and fix bugs in Joomla. This includes the following:
+
{{browsebar|bugsquad}}<div style="clear:both; width:100%">
 
+
{{:{{FULLPAGENAME}}/box-header-sq|Introduction to the Joomla! {{PAGENAME}}|{{FULLPAGENAME}}/Intro|}}
* Scan the [http://forum.joomla.org/viewforum.php?f=199 Joomla! Bug Reporting Forum] and [http://forum.joomla.org/viewforum.php?f=579 Joomla! 1.6 Beta Bug Reporting Forum] for reported issues and help community members with solving these issues.
+
{{:{{FULLPAGENAME}}/Intro}}
* Maintaining the [[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=32 Version 1.5 Bug Tracker]] and [[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker]] .
+
{{:{{FULLPAGENAME}}/box-footer|}}
* Fix reported bugs and resolve reported issues according to the [[Bug Tracking Process]].
+
</div>
 
+
<div style="clear:both; width:100%"></div>
The Bug Squad is also supporting with testing and quality assurance when a new major or minor version is developed. Generally speaking the bug-squad is in the lead when a version switches from beta-stage to the stable-stage within the development cycle of Joomla!
+
<div class="portal-column-left"> <!-- Switch to one column on narrow screens -->
 
+
{{:{{FULLPAGENAME}}/box-header-sq|Bug Squad Background|{{FULLPAGENAME}}/History|}}
The Bug Squad was created in December 2007. As of May 2010, JBS has been organised into the following teams:
+
{{:{{FULLPAGENAME}}/History}}
* Tracker Team - monitors the forums and trackers
+
{{:{{FULLPAGENAME}}/box-footer|}}
* Coding Team - creates patches for Confirmed Issues
+
</div>
* Testing Team - tests Pending issues
+
<div class="portal-column-right"> <!-- Switch to one column on narrow screens -->
* Automated Testing Team - creates automated system and unit tests for tracker issues
+
{{:{{FULLPAGENAME}}/box-header-sq|Contacts|{{FULLPAGENAME}}/Contacts|}}
* Migration / Upgrade Team - responsible for supporting migration and upgrading from the prior version to the current version.
+
{{:{{FULLPAGENAME}}/Contacts}}
 
+
{{:{{FULLPAGENAME}}/box-footer|}}
These teams are not rigid, and JBS members can participate in whatever activities they wish. The purpose of the teams is to make it easier for JBS members to focus their efforts and learn the skills required to successfully contribute to the project.
+
</div>
 
+
<div style="clear:both; width:100%">
If you are a member of the JBS, you might also like to join the JBS group at [http://people.joomla.org/groups/viewgroup/95-Joomla+Bug+Squad.html people.joomla.org].
+
{{:{{FULLPAGENAME}}/box-header-sq-noedit|Meet the Bug Squad Teams|blank edit link|}}
 
+
The following is a list of all the Bug Squad Teams and a brief description of what each one does. Use the contact information found above if you would like to help the Bug Squad or become a JBS member!
===Tracker Team===
+
<div style="clear:both; width:100%">
This team has the very important and sometimes difficult job of filtering all of the forum posts and bug reports and sorting out which ones are real bugs that are ready to be worked on. From the standpoint of the tracker, their job is to move issues from Open status to Confirmed status. Of course, many issues will also be put into other status codes, including Information Required, Needs Review, Duplicate, Not a Bug, and so on.
+
{{:{{FULLPAGENAME}}/box-header-sq|Tracker Team|Bug Squad Tracker Team|}}
 
+
{{:Bug Squad Tracker Team}}
Before an issue is marked Confirmed, it needs to be reproduced and documented so that others can reproduce the problem.
+
{{:{{FULLPAGENAME}}/box-footer|For more information see the [[Bug Squad Tracker Team|Tracker Team]] page}}
 
+
{{:{{FULLPAGENAME}}/box-header-sq|Coding Team|Bug Squad Coding Team|}}
The Tracker Team should also make sure the issue has the correct Type and Priority. Remember, many users reporting bugs are not familiar with all of the fields and terminology. In many cases, this could be the user's first contribution or interaction with the project.
+
{{:Bug Squad Coding Team}}
 
+
{{:{{FULLPAGENAME}}/box-footer|For more information see the [[Bug Squad Coding Team|Coding Team]] page.}}
It is critically important that all JBS members follow the Code of Conduct and show courtesy and respect in all tracker comments. Remember, we are the ambassadors of the Joomla! project, and the way we behave reflects on the whole project. People will naturally be unhappy if an issue they report is not taken seriously or if they feel that it was closed improperly. So we need to be sensitive to that fact, while of course making the what we believe to be the correct decision. For example, if you close an issue as Not a Bug, please put a comment in telling the reporter why in a nice way.
+
{{:{{FULLPAGENAME}}/box-header-sq|Testing Team|Bug Squad Testing Team|}}
 
+
{{:Bug Squad Testing Team}}
Also, if someone is not following the Code of Conduct in a tracker comment, please point this out in a respectful way and remind the person that we need to follow the CoC at all times. If there is a persistent problem, please let your Team Leader or a JBS Coordinator know so we can take action. We absolutely do not want to tolerate rude or disrespectful behavior in the tracker or forum.
+
{{:{{FULLPAGENAME}}/box-footer|For more information see the [[Bug Squad Testing Team|Testing Team]] page.}}
 
+
{{:{{FULLPAGENAME}}/box-header-sq|Automated Testing Team|Bug Squad Automated Testing Team|}}
For more information see the [[Tracker Team]] page.
+
{{:Bug Squad Automated Testing Team}}
 
+
{{:{{FULLPAGENAME}}/box-footer|For more information see the [[Bug Squad Automated Testing Team|Automated Testing Team]] page.}}
===Coding Team===
+
{{:{{FULLPAGENAME}}/box-header-sq|Migration and Update Team|{{FULLPAGENAME}}/Migration and Update Team|}}
The coding team works with Confirmed issues and creates patches to correct these issues if they haven't already been provided. When a patch is completed, and when a test plan has been added that tells the testers how to test the patch, the issue is changed to Pending status.
+
{{:{{FULLPAGENAME}}/Migration and Update Team}}
 
+
{{:{{FULLPAGENAME}}/box-footer|}}
Many times the first patch submitted for an issue will not be the actual patch that is committed to the SVN. There are many reasons for this. Someone else may have a different approach to the solving the issue, a tester might find a problem, or the person who submitted the patch will think of a better way to do it.
+
</div>
 
+
{{:{{FULLPAGENAME}}/box-footer|}}
It is important to be positive and flexible and not expect that every patch you submit will go straight into the SVN. That does not mean the work is not helpful or valuable. In many cases, it is not possible to get to the end result without going through one or more tries.
+
</div>
 
+
<div style="clear:both; width:100%"></div>
For more information see the [[Bug Squad Coding Team]] page.
+
</div><!-- top div close -->
 
+
__NOTOC__ __NOEDITSECTION__
===Testing Team===
+
<noinclude>[[Category:Working Groups]][[Category:Permanent Working Groups]][[Category:Bug Squad]]</noinclude>
This team tests Pending issues and, when tests are successful, documents this and moves the issue to Ready to Commit status. At this point, one of the JBS coordinators will commit the patch to the SVN.
+
 
+
Over time, we plan to include more automated testing into the process. Eventually, we would like every Ready to Commit issue have both a code patch and an automated system or unit test. Accordingly, it will be important for members of the testing team to be learning how to write and use system tests.
+
 
+
There are some tips for testing in the wiki in the [[Testing Checklists]] article.
+
 
+
===Automated Testing Team===
+
Automated testing is a key technology that we will incorporate into the workings of JBS. At the present, this is a somewhat specialized skill, so we will start by developing a separate team of people who are familiar with this and can help write automated tests and train other JBS members on automated testing. Our aim is to eventually make automated testing a routine part of fixing issues.
+
 
+
For more information see the [[Automated Testing Team]] page.
+
 
+
===Migration / Upgrade Team===
+
This team is responsible for coding and documenting the upgrade process for users migrating sites or extensions from one version to the next (for example, from version 1.5 to 1.6). They will be responsible for creating and fixing issues in this area of the code.
+
 
+
===Contacts===
+
;Joomla! Bug Squad Coordinators : [mailto:mark.dexter@community.joomla.org Mark Dexter]
+
 
+
;To request to join the Bug Squad :[mailto:mark.dexter@community.joomla.org Mark Dexter]
+
;Tracker Team Leaders: [mailto:elin.waring@gmail.com Elin Waring]
+
;Coding Team Leaders:
+
: [mailto:orware@gmail.com Omar Ramos]
+
;Testing Team Leaders : [mailto:marijkestuivenberg@gmail.com Marijke Stuivenberg]
+
;Automated Testing Team Leaders : to be announced
+
<noinclude>[[Category:Development Working Group]][[Category:Bug Squad]]</noinclude>
+
[[Category:Working Groups]]
+

Revision as of 15:11, 28 November 2012

JBS Portal Page · Bug Squad · Tracker Team · Coding Team · Testing Team · Automated Testing Team

Introduction to the Joomla! Bug Squad

Workgroups bugsquad.jpg

The Joomla! Bug Squad (JBS) is a team within the Production Working Groups. Their job is to identify and fix bugs in Joomla. This includes the following:

The Bug Squad is also supporting with testing and quality assurance when a new major or minor version is developed. Generally speaking the bug-squad is in the lead when a version switches from beta-stage to the stable-stage within the development cycle of Joomla!

Bug Squad Background

The Bug Squad was created in December 2007. As of May 2010, JBS has been organised into the following teams:

These teams are not rigid, and JBS members can participate in whatever activities they wish. The purpose of these teams are to make it easier for the JBS members to focus their efforts and learn the skills required to successfully contribute to the project.

Contacts

Joomla! Bug Squad Coordinator
Nick Savov
PLT Contact
Nick Savov
To request to join the Bug Squad
Nick Savov
Tracker Team Leaders
Open
Coding Team Leaders
Open
Testing Team Leaders
Open
Automated Testing Team Leaders
Open

Meet the Bug Squad Teams

The following is a list of all the Bug Squad Teams and a brief description of what each one does. Use the contact information found above if you would like to help the Bug Squad or become a JBS member!

Tracker Team

This team has the very important and sometimes difficult job of filtering all of the forum posts and bug reports and sorting out which ones are real bugs that are ready to be worked on. From the standpoint of the tracker, their job is to move issues from Open status to Confirmed status. Of course, many issues will also be put into other status codes, including Information Required, Needs Review, Duplicate, Not a Bug, and so on.

Before an issue is marked Confirmed, it needs to be reproduced and documented so that others can reproduce the problem.

The Tracker Team should also make sure the issue has the correct Type and Priority. Remember, many users reporting bugs are not familiar with all of the fields and terminology. In many cases, this could be the user's first contribution or interaction with the project.

For more information see the Tracker Team page

Coding Team

The coding team works with Confirmed issues and creates patches to correct these issues if they haven't already been provided. When a patch is completed, and when a test plan has been added that tells the testers how to test the patch, the issue is changed to Pending status.

Many times the first patch submitted for an issue will not be the actual patch that is committed. There are many reasons for this. Someone else may have a different approach to the solving the issue, a tester might find a problem, or the person who submitted the patch will think of a better way to do it.

It is important to be positive and flexible and not expect that every patch you submit will go straight into the SVN. That does not mean the work is not helpful or valuable. In many cases, it is not possible to get to the end result without going through one or more tries.

For more information see the Coding Team page.

Testing Team


This team tests Pending issues and, when tests are successful, documents this and moves the issue to Ready to Commit status. At this point, one of the JBS coordinators will commit the patch to the SVN.

Over time, we plan to include more automated testing into the process. Eventually, we would like every Ready to Commit issue have both a code patch and an automated system or unit test. Accordingly, it will be important for members of the testing team to be learning how to write and use system tests.

There are some tips for testing in the wiki in the Testing Checklists article.

For more information see the Testing Team page.

Automated Testing Team

Automated testing is a key technology that we will incorporate into the workings of JBS. At the present, this is a somewhat specialized skill, so we will start by developing a separate team of people who are familiar with this and can help write automated tests and train other JBS members on automated testing. Our aim is to eventually make automated testing a routine part of fixing issues.

For more information see the Automated Testing Team page.

Migration and Update Team

This team is responsible for coding and documenting the upgrade process for users migrating sites or extensions from one version to the next (for example, from version 1.5 to 2.5). They will be responsible for creating and fixing issues in this area of the code.