Bug Squad/Geschiedenis
From Joomla! Documentation
Revision as of 12:43, 31 March 2017 by Fcschippers (talk | contribs) (Created page with "Het uitbrengen van Joomla! 1.5 Beta2 was het begin van de transitie van het leiden van het ontwikkelproces van de Development werkgroep naar het leiden van het ontwikkelproces...")
Kort na het ontstaan van Joomla!, werd de Quality & Testing Working Group opgezet[1] met als doel het testen en evalueren van major en minor releases met betrekking tot beveiliging, stabiliteit en performance problemen. Het team organiseert, verwerkt en test rapportages en suggesties vanuit de community, met als doel het verder verbeteren van de code base tussen de major en minor releases[2].
Het uitbrengen van Joomla! 1.5 Beta2 was het begin van de transitie van het leiden van het ontwikkelproces van de Development werkgroep naar het leiden van het ontwikkelproces door de Quality & Testing werkgroep[3]. De focus is toen officieel verschoven van nieuwe functies naar stabiliteit en beveiliging. Helaas, als gevolg van de lange periode (zonder voortgang) tussen de release van Joomla! 1.0.12 en de transitie van het leiden van het ontwikkelproces naar het Quality & Testing team voor de Joomla! 1.5 cyclus, zijn veel leden van het Quality & Testing team vertrokken. Het team was overbelast door het proces, waardoor uiteindelijk de Quality & Testing werkgroep in september 2007 is ontbonden[4].
To fill the gap, the first Pizza, Bugs and Fun event was organised[5], with Joomlers gathering in New York, San Francisco, Washington DC, Vancouver and Brussels in the beginning of December 2007. In three days around 100 commits were processed and 88 artifacts closed[6].
During the PBF event, the idea for a new team was born. The team was called "The Bug Squad", and should help out organising the handling of the feedback process, keep the tracker up to date, perform testing, guide people in the forums and during PBF events, and provide patches to the Development Working Group, to which the Bug Squad would be a sub-team[7].
In May 2010, the Joomla! Bug Squad (JBS) had been organised into the different teams: a Tracker Team to monitors the forums and trackers, a Coding Team to create patches for confirmed issues, a Testing Team to test pending issues, an Automated Testing Team to create automated system and unit tests for tracker issues, and a Migration and Upgrade Team to support migration and upgrading from the prior version to the current version.
In the following years, the team structures changed a lot. The introduction of the Volunteers Portal made most of the working groups bubble to the main level. A System Testing Working Group and a Unit Testing Working Group were created and in January 2015 combined into the Automated Testing Working Group on the same organisational level as the Bug Squad. Specific Release teams were in charge to support migration and upgrades.
With the transition to the new structure, in January 2017, the Joomla! Bug Squad had to redefine its purpose, function and roles as any other team in the Production Department. That was an opportunity for the JBS to bethink itself of its origin. While the purpose still was to reduce the number of bugs in Joomla, not only for the CMS, but for every Joomla project, helping and mentoring developers and contributors with bug squashing got more importance.