| The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.
Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.
Difference between revisions of "Bugzilla"
(Obsoleted - Bugzilla has been dismissed)
|(36 intermediate revisions by 11 users not shown)|
|Line 1:||Line 1:|
is to share the
of bugs Waze , and to the they , .
Latest revision as of 15:08, 17 February 2015
|This information is obsolete and the active links to this page have been reviewed for disconnection or replacement. More current alternate information is likely available and should be followed rather than this information.|
Bugzilla is an external issue tracking system formerly used internally by Waze technical teams. As of August 2014[update], Waze has ceased using Bugzilla to share information about bugs and features with the Waze community.
The Waze installation of Bugzilla was formerly viewable to the entire Waze community. Public bugs and feature requests were viewable by the entire world, while Internal bugs and features were viewable only by Waze staff. Select experienced members of the Waze community (Local and Global Champs, Experts, Coordinators, and WME beta-testers) could log in to bugzilla, add comments about bugs and features, and vote for the items they felt were most critical. In addition, a select few bug submitters were hand-picked by the Waze staff. They could read bug/testing discussions on the forums and create new bug reports.