[go: nahoru, domu]
Jump to content

Bugzilla: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
m Filled in 1 bare reference(s) with reFill ()
→Requirements: added MariaDB
(46 intermediate revisions by 33 users not shown)
Line 1:
{{short description|Web-based general-purpose bugtracker}}{{primary sources|date=September 2011}}
{{Infobox software
| name =
| title = Bugzilla
| logo = BuggieBugzilla newlogo (2022).pngsvg
| logo caption = '''Buggie''', Mascotthe mascot of ''Bugzilla''.
| logo size = 100px
| logo alt = Buggie, Mascot of Bugzilla
| screenshot = BugzillaScreenshotBugzilla.mozilla.org screenshot.png
| caption = Bugzilla in action on {{URL|https://bugzilla.mozilla.org}}
| screenshot size = 350px
Line 14 ⟶ 13:
| author = Terry Weissman
| developer = [[Mozilla Foundation]]
| released = {{Start date and age|1998|08|26}}<ref>{{cite web | url = https://groups.google.com/group/netscape.public.mozilla.announce/browse_thread/thread/b52aa841db9f7e9b/f10c0f781841f10d#f10c0f781841f10d | title = New version of "Bugzilla" (the mozilla.org bugsystem) – with source! | publisher = netscape.public.mozilla.announce | accessdateaccess-date = 2011-01-28 }}</ref>
| discontinued =
| latest release version = {{Latest stable software release/Bugzilla}}<!-- Release version update? Don't edit this page, just click on the version number! -->
Line 29 ⟶ 28:
| license = [[Mozilla Public License]]
| alexa =
| website = {{URL|httphttps://www.bugzilla.org/}}
}}
'''Bugzilla''' is a [[World Wide Web|web]]-based general-purpose [[bugtrackerbug tracking system]] and [[Test automation|testing tool]] originally developed and used by the [[Mozilla]] project, and [[software license|licensed]] under the [[Mozilla Public License]].
 
Released as [[open-source software]] by [[Netscape Communications]] in 1998, it has been adopted by a variety of organizations for use as a [[bug tracking system]] for both [[free and open-source software]] and [[proprietary software|proprietary]] projects and products. Bugzilla is used, among others, by the [[Mozilla Foundation]], [[WebKit]], [[Linux kernel]], [[FreeBSD]],<ref>{{cite web|url=https://lists.freebsd.org/pipermail/freebsd-announce/2014-June/001559.html|title=Announcement of Migration from GNATS to Bugzilla on the FreeBSD mailing list|date=3 June 2014 |quote=Bugzilla supports finer granularity for categories and keywords and over time we will adopt more of these, making it easier to filter bugs into specific target areas. It is now easy for multiple people to track a single bug, without having to have them assigned to custom mailing lists, add attachments to bugs, and so on. Many features that people expect from a modern bug tracker are simply not present in GNATS.}}</ref> [[GNOME]], [[KDE]], [[Apache Software Foundation|Apache]], [[Red Hat]], [[Eclipse (software)|Eclipse]] and [[LibreOffice]].<ref>{{cite web|url=http://www.bugzilla.org/installation-list/|title=Installation List|work=bugzilla.org}}</ref> Red Hat uses it, but is gradually migrating its product to use [[Jira (software)|Jira]].<ref>{{Cite web |title=[CentOS-devel] RHEL moving to issues.redhat.com only long term |url=https://lists.centos.org/pipermail/centos-devel/2022-March/120269.html |access-date=2022-04-19}}</ref><ref>{{Cite web |title=CentOS Community Newsletter, April 2022 – Blog.CentOS.org |url=https://blog.centos.org/2022/04/centos-community-newsletter-april-2022/ |access-date=2022-04-19 |language=en-US}}</ref> It is also [[Self-hosting (compilers)|self-hosting]].<ref>{{Cite web|url = http://www.bugzilla.org/developers/reporting_bugs.html|title = Reporting Bugs|date = 31 December 2014|accessdateaccess-date = 9 January 2014|website = Bugzilla|publisher = Bugzilla}}</ref>
 
== History ==
 
Bugzilla was originally devised by Terry Weissman in 1998 for the nascent [[Mozilla.org]] project, as an [[Open-source software|open source]] application to replace the in-house system then in use at Netscape Communications for tracking defects in the [[Netscape Communicator]] suite. Bugzilla was originally written in [[Tcl]], but Weissman decided to port it to [[Perl]] before its release as part of Netscape's early open -source code drops, in the hope that more people would be able to contribute to it, given that Perl seemed to be a more popular language at the time.<ref>{{cite web | url = http://www.bugzilla.org/status/roadmap.html#history | title = Brief History | work = Development Roadmap | publisher = Mozilla.org | accessdateaccess-date = 2006-11-22 }}</ref>
 
Bugzilla 2.0 was the result of that port to Perl, and the first version was released to the public via anonymous [[Concurrent Versions System|CVS]]. In April 2000, Weissman handed over control of the Bugzilla project to [[Tara Hernandez]]. Under her leadership, some of the regular contributors were coerced into taking more responsibility, and Bugzilla development became more community-driven. In July 2001, facing distraction from her other responsibilities in Netscape, Hernandez handed control to Dave Miller, who was still in charge {{as of|20132020|lc=on}}.<ref name="bugzilla-dev-profiles">{{cite web | url = http://www.bugzilla.org/developers/profiles.html | title = Developer Profiles | work = Bugzilla Website | publisher = Mozilla.org | accessdateaccess-date = 2013-07-02 }}</ref>
 
Bugzilla 3.0 was released on May 10, 2007 and brought a refreshed [[User interface|UI]], an [[XML-RPC]] interface, custom fields and resolutions, [[mod_perl]]<!-- THE UNDERSCORE IS DELIBERATE --> support, shared saved searches, and improved [[UTF-8]] support, along with other changes.
 
Bugzilla 4.0 was released on February 15, 2011 and Bugzilla 5.0 was released in July 2015.
 
=== Timeline ===
 
Bugzilla's release timeline:<ref>{{cite web |url = http://www.bugzilla.org/releases/ |title = Release Dates |work=Release Information |publisher=Mozilla.org |accessdateaccess-date=2011-03-31 }}</ref>
 
<timeline>
Define $now = 2422/0102/20192021
Define $width = 556
Define $warning = 436 # $width – 120
Line 447 ⟶ 446:
at: 16/05/2016 text:"5.0.3"
at: 16/02/2018 text:"5.0.4"
at: 30/01/2019 text:"5.0.5"
 
##################################################
Line 454:
at: 10/09/2015 # 5.0.1
at: 22/12/2015 # 5.0.2
at: 09/02/2019 # 5.0.6
 
TextData =
Line 473 ⟶ 474:
* A suitable [[mail transfer agent]], or any [[SMTP]] server
 
Currently supported database systems are [[MariaDB]], [[MySQL]], [[PostgreSQL]], [[Oracle Database|Oracle]], and [[SQLite]].<ref>{{Cite web |title=3.6.1. MySQL — Bugzilla 5.0.6 documentation |url=https://bugzilla.readthedocs.io/en/latest/installing/mysql.html |access-date=2024-05-13 |website=bugzilla.readthedocs.io}}</ref> Bugzilla is usually installed on [[Linux]] using the [[Apache HTTP Server]], but any web server that supports [[Common Gateway Interface|CGI]] such as [[Lighttpd]], [[Hiawatha (web server)|Hiawatha]], [[Cherokee (web server)|Cherokee]] can be used. Bugzilla's installation process is [[command line]] driven and runs through a series of stages where system requirements and software capabilities are checked.
 
== Design ==
[[Image:Bugzilla Lifecycle color-aqua.svg|thumb|270px|The lifecyclelife cycle of a Bugzilla bug]]
 
While the potential exists in the code to turn Bugzilla into a [[issue tracking system|technical support ticket system]], task management tool, or project management tool, Bugzilla's developers have chosen to focus on the task of designing a system to track software defects. Mandated design requirements include:<ref>{{cite web | url = http://www.bugzilla.org/status/roadmap.html#design | title = Design Principles | work = Development Roadmap | publisher = Mozilla.org | accessdate = 2006-11-22 }}</ref>
 
* The ability to run on freely available, open-source tools. While Bugzilla development includes work to support commercial databases, tools, and operating systems.
* The maintenance of speed and efficiency at all costs. One of Bugzilla's major attractions to developers is its lightweight implementation and speed, so calls into the database are minimized whenever possible, data fetching is kept as light as possible, and generation of heavy [[HTML]] is avoided.{{Citation needed|date=September 2011}}
* Tickets. For instance, Mozilla.org uses it to track feature requests as well. In this case items (called bugs) can be submitted by anybody, and will be assigned to a particular developer. Various status updates for each bug are allowed, together with user notes and bug examples.
 
In practice, most Bugzilla projects allowing the public to file bugs&mdash;such as the Bugzilla bug database for Bugzilla itself&mdash;assign all bugs to a gatekeeper, whose job it is to assign responsibility and priority level.
 
== Zarro Boogs ==
<!-- linked from redirect [[Zarro boogs]] -->
By design, Bugzilla is programmed to returnreturns the string "zarro boogs found" instead of "0 bugs found" when a search for bugs returns no results.<ref name="zarro">{{cite web | url = http://www.bugzilla.org/docs/3.0/html/glossary.html#gloss-zarro | title = Bugzilla Guide glossary entry for ''Zarro Boogs Found'' | work = Glossary | publisher = Bugzilla.org | accessdateaccess-date = 2008-04-21}}</ref> "Zarro Boogs" is intended as a meta-'buggy' statement aboutitself the(a naturemisspelling of software [[software bug|debugging]]. [[Bug tracking system]]s like Bugzilla readily describe how many ''known''"zero bugs")<ref are outstanding. The response name="zarro" boogs",/><ref>Coined by Michael Toy as explained by Tara Hernandez in the [[PBS]] documentary {{cite video | title=[[Code Rush]] | time=18:21 }}</ref> and is intended asthus a buggy meta-statement itselfabout (athe misspellingnature of "zerosoftware bugs")[[debugging]], implying that even when no bugs have been identified, softwaresome ismay still likely to contain bugs that have not yet been identifiedexist.<ref name="zarro" />
 
The following comment is provided in the Bugzilla source code to developers who may be confused by this behaviour:
Line 495 ⟶ 490:
:This is just a goofy way of saying that there were no bugs found matching your query. When asked to explain this message, Terry Weissman (an early Bugzilla developer) had the following to say:
 
:I've been asked to explain this ... way back when, when Netscape released version 4.0 of its browser, we had a release party. Naturally, there had been a big push to try and fix every known bug before the release. Naturally, that hadn't actually happened. (This is not unique to Netscape or to 4.0; the same thing has happened with every software project I've ever seen.) Anyway, at the release party, T-shirts were handed out that said something like "Netscape 4.0: Zarro Boogs". Just like the software, the T-shirt had no known bugs. Uh-huh. So, when you query for a list of bugs, and it gets no results, you can think of this as a friendly reminder. Of *course* there are bugs matching your query, they just aren't in the bugsystem yet...
:— Terry Weissman
:''From The Bugzilla Guide – 2.16.10 Release: Glossary''<ref>{{cite web|url=https://www.bugzilla.org/docs/2.16/html/glossary.html|title=Glossary|website=www.bugzilla.org}}</ref>
Line 501 ⟶ 496:
==WONTFIX==
<!-- linked from redirects [[WONTFIX]] and [[Wontfix]]-->
WONTFIX is used as a label on issues in Bugzilla and other systems.<ref name="opensuse">{{cite web|title=Bug Status WONTFIX - openSUSE|url=https://en.opensuse.org/Bug_Status_WONTFIX|website=en.opensuse.org|accessdateaccess-date=9 May 2018|language=en}}</ref> It indicates that a verified issue will not be addressed for one of several possible reasons including fixing would be too expensive, complicated or risky.<ref>{{cite web |url=https://developer.mozilla.org/en-US/docs/Mozilla/Bugzilla/What_to_do_and_what_not_to_do_in_Bugzilla |title=What to do and what not to do in Bugzilla |access-date=2018-05-09 |archive-date=2018-06-29 |archive-url=https://web.archive.org/web/20180629235829/https://developer.mozilla.org/en-US/docs/Mozilla/Bugzilla/What_to_do_and_what_not_to_do_in_Bugzilla |url-status=dead }}</ref><ref>{{cite web |url=https://developer.mozilla.org/en-US/docs/Mozilla/Bugzilla/What_to_do_and_what_not_to_do_in_Bugzilla |title=Bug Status WONTFIX |access-date=2018-05-09 |archive-date=2018-06-29 |archive-url=https://web.archive.org/web/20180629235829/https://developer.mozilla.org/en-US/docs/Mozilla/Bugzilla/What_to_do_and_what_not_to_do_in_Bugzilla |url-status=dead }}</ref>
 
== See also ==
{{Portal|Free and open-source software|Software Testing}}
 
* [[Comparison of issue-tracking systems]]
Line 511 ⟶ 506:
 
== References ==
{{reflistReflist}}
 
== External links ==
{{Commons category}}
{{commonscatinline}}
*{{Official website|http://www.bugzilla.org}}
 
{{Bug tracking systems}}

Revision as of 08:09, 13 May 2024

Bugzilla
Original author(s)Terry Weissman
Developer(s)Mozilla Foundation
Initial releaseAugust 26, 1998; 26 years ago (1998-08-26)[1]
Stable release
5.0.6 (February 9, 2019; 5 years ago (2019-02-09)[2]) [±]

4.4.13 (February 16, 2018; 6 years ago (2018-02-16)[2]) [±]

Preview release5.1.2 (February 16, 2018; 6 years ago (2018-02-16)[3]) [±]
Repository
Written inPerl
Operating systemCross-platform
Available inMultiple languages
TypeBug tracking system
LicenseMozilla Public License
Websitewww.bugzilla.org

Bugzilla is a web-based general-purpose bug tracking system and testing tool originally developed and used by the Mozilla project, and licensed under the Mozilla Public License.

Released as open-source software by Netscape Communications in 1998, it has been adopted by a variety of organizations for use as a bug tracking system for both free and open-source software and proprietary projects and products. Bugzilla is used, among others, by the Mozilla Foundation, WebKit, Linux kernel, FreeBSD,[4] KDE, Apache, Eclipse and LibreOffice.[5] Red Hat uses it, but is gradually migrating its product to use Jira.[6][7] It is also self-hosting.[8]

History

Bugzilla was originally devised by Terry Weissman in 1998 for the nascent Mozilla.org project, as an open source application to replace the in-house system then in use at Netscape Communications for tracking defects in the Netscape Communicator suite. Bugzilla was originally written in Tcl, but Weissman decided to port it to Perl before its release as part of Netscape's early open-source code drops, in the hope that more people would be able to contribute to it, given that Perl seemed to be a more popular language at the time.[9]

Bugzilla 2.0 was the result of that port to Perl, and the first version was released to the public via anonymous CVS. In April 2000, Weissman handed over control of the Bugzilla project to Tara Hernandez. Under her leadership, some of the regular contributors were coerced into taking more responsibility, and Bugzilla development became more community-driven. In July 2001, facing distraction from her other responsibilities in Netscape, Hernandez handed control to Dave Miller, who was still in charge as of 2020.[10]

Bugzilla 3.0 was released on May 10, 2007 and brought a refreshed UI, an XML-RPC interface, custom fields and resolutions, mod_perl support, shared saved searches, and improved UTF-8 support, along with other changes.

Bugzilla 4.0 was released on February 15, 2011 and Bugzilla 5.0 was released in July 2015.

Timeline

Bugzilla's release timeline:[11]

Requirements

Bugzilla's system requirements include:

Currently supported database systems are MariaDB, MySQL, PostgreSQL, Oracle, and SQLite.[12] Bugzilla is usually installed on Linux using the Apache HTTP Server, but any web server that supports CGI such as Lighttpd, Hiawatha, Cherokee can be used. Bugzilla's installation process is command line driven and runs through a series of stages where system requirements and software capabilities are checked.

Design

The life cycle of a Bugzilla bug

While the potential exists in the code to turn Bugzilla into a technical support ticket system, task management tool, or project management tool, Bugzilla's developers have chosen to focus on the task of designing a system to track software defects.

Zarro Boogs

Bugzilla returns the string "zarro boogs found" instead of "0 bugs found" when a search for bugs returns no results.[13] "Zarro Boogs" is intended as a 'buggy' statement itself (a misspelling of "zero bugs")[13][14] and is thus a meta-statement about the nature of software debugging, implying that even when no bugs have been identified, some may exist.

The following comment is provided in the Bugzilla source code to developers who may be confused by this behaviour:

Zarro Boogs Found
This is just a goofy way of saying that there were no bugs found matching your query. When asked to explain this message, Terry Weissman (an early Bugzilla developer) had the following to say:
I've been asked to explain this ... way back when, when Netscape released version 4.0 of its browser, we had a release party. Naturally, there had been a big push to try and fix every known bug before the release. Naturally, that hadn't actually happened. (This is not unique to Netscape or to 4.0; the same thing has happened with every software project I've ever seen.) Anyway, at the release party, T-shirts were handed out that said something like "Netscape 4.0: Zarro Boogs". Just like the software, the T-shirt had no known bugs. Uh-huh. So, when you query for a list of bugs, and it gets no results, you can think of this as a friendly reminder. Of *course* there are bugs matching your query, they just aren't in the bugsystem yet...
— Terry Weissman
From The Bugzilla Guide – 2.16.10 Release: Glossary[15]

WONTFIX

WONTFIX is used as a label on issues in Bugzilla and other systems.[16] It indicates that a verified issue will not be addressed for one of several possible reasons including fixing would be too expensive, complicated or risky.[17][18]

See also

References

  1. ^ "New version of "Bugzilla" (the mozilla.org bugsystem) – with source!". netscape.public.mozilla.announce. Retrieved 2011-01-28.
  2. ^ a b "[ 2019 Feb 09 ] Release Information". 2019-02-09. Retrieved 2019-05-15.
  3. ^ "[ 2018 Feb 16 ] Release of Bugzilla 5.1.2, 5.0.4, and 4.4.13". 2018-02-16. Retrieved 2018-02-24.
  4. ^ "Announcement of Migration from GNATS to Bugzilla on the FreeBSD mailing list". 3 June 2014. Bugzilla supports finer granularity for categories and keywords and over time we will adopt more of these, making it easier to filter bugs into specific target areas. It is now easy for multiple people to track a single bug, without having to have them assigned to custom mailing lists, add attachments to bugs, and so on. Many features that people expect from a modern bug tracker are simply not present in GNATS.
  5. ^ "Installation List". bugzilla.org.
  6. ^ "[CentOS-devel] RHEL moving to issues.redhat.com only long term". Retrieved 2022-04-19.
  7. ^ "CentOS Community Newsletter, April 2022 – Blog.CentOS.org". Retrieved 2022-04-19.
  8. ^ "Reporting Bugs". Bugzilla. 31 December 2014. Retrieved 9 January 2014.
  9. ^ "Brief History". Development Roadmap. Mozilla.org. Retrieved 2006-11-22.
  10. ^ "Developer Profiles". Bugzilla Website. Mozilla.org. Retrieved 2013-07-02.
  11. ^ "Release Dates". Release Information. Mozilla.org. Retrieved 2011-03-31.
  12. ^ "3.6.1. MySQL — Bugzilla 5.0.6 documentation". bugzilla.readthedocs.io. Retrieved 2024-05-13.
  13. ^ a b "Bugzilla Guide glossary entry for Zarro Boogs Found". Glossary. Bugzilla.org. Retrieved 2008-04-21.
  14. ^ Coined by Michael Toy as explained by Tara Hernandez in the PBS documentary Code Rush. Event occurs at 18:21.
  15. ^ "Glossary". www.bugzilla.org.
  16. ^ "Bug Status WONTFIX - openSUSE". en.opensuse.org. Retrieved 9 May 2018.
  17. ^ "What to do and what not to do in Bugzilla". Archived from the original on 2018-06-29. Retrieved 2018-05-09.
  18. ^ "Bug Status WONTFIX". Archived from the original on 2018-06-29. Retrieved 2018-05-09.
Wikimedia Commons has media related to Bugzilla.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Bugzilla&oldid=1223614684"