/[gentoo]/xml/htdocs/doc/en/bugzilla-howto.xml
Gentoo

Diff of /xml/htdocs/doc/en/bugzilla-howto.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.8 Revision 1.9
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.8 2006/11/10 22:19:40 nightmorph Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.9 2007/02/14 21:30:15 nightmorph Exp $ -->
4 4
5<guide link="/doc/en/bugzilla-howto.xml"> 5<guide link="/doc/en/bugzilla-howto.xml">
6<title>Gentoo Bug Reporting Guide</title> 6<title>Gentoo Bug Reporting Guide</title>
7 7
8<author title="Author"> 8<author title="Author">
9 <mail link="chriswhite@gentoo.org">Chris White</mail> 9 <mail link="chriswhite@gentoo.org">Chris White</mail>
10</author> 10</author>
11<author title="Editor"> 11<author title="Editor">
12 <mail link="fox2mike@gentoo.org">Shyam Mani</mail> 12 <mail link="fox2mike@gentoo.org">Shyam Mani</mail>
13</author> 13</author>
14 14
15<abstract> 15<abstract>
16This document shows the proper method of reporting bugs using Bugzilla. 16This document shows the proper method of reporting bugs using Bugzilla.
17</abstract> 17</abstract>
18 18
19<!-- The content of this document is licensed under the CC-BY-SA license --> 19<!-- The content of this document is licensed under the CC-BY-SA license -->
20<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 20<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
21<license/> 21<license/>
22 22
23<version>1.7</version> 23<version>1.8</version>
24<date>2006-11-10</date> 24<date>2007-02-14</date>
25 25
26<chapter> 26<chapter>
27<title>Introduction</title> 27<title>Introduction</title>
28<section> 28<section>
29<title>Preface</title> 29<title>Preface</title>
30<body> 30<body>
31 31
32<p> 32<p>
33One of the factors that delay a bug being fixed is the way it is reported. By 33One of the factors that delay a bug being fixed is the way it is reported. By
34creating this guide, we hope to help improve the communication between 34creating this guide, we hope to help improve the communication between
35developers and users in bug resolution. Getting bugs fixed is an important, if 35developers and users in bug resolution. Getting bugs fixed is an important, if
36not crucial part of the quality assurance for any project and hopefully this 36not crucial part of the quality assurance for any project and hopefully this
37guide will help make that a success. 37guide will help make that a success.
38</p> 38</p>
39 39
946 946
947<p> 947<p>
948Here, we'll set it to Normal. 948Here, we'll set it to Normal.
949</p> 949</p>
950 950
951<p> 951<p>
952Now we can submit the bug report by clicking on the Submit Bug Report box. You 952Now we can submit the bug report by clicking on the Submit Bug Report box. You
953will now see your new bug come up. See <uri 953will now see your new bug come up. See <uri
954link="https://bugs.gentoo.org/show_bug.cgi?id=97265">Bug 97561</uri> for what 954link="https://bugs.gentoo.org/show_bug.cgi?id=97265">Bug 97561</uri> for what
955the result looks like. We've reported our bug! Now let's see how it's dealt 955the result looks like. We've reported our bug! Now let's see how it's dealt
956with. 956with.
957</p> 957</p>
958 958
959</body> 959</body>
960</section> 960</section>
961<section>
962<title>Zero-day bump requests</title>
963<body>
964
965<p>
966So far, we've shown what to do when filing a bug. Now let's take a look at what
967<e>not</e> to do.
968</p>
969
970<p>
971Suppose that you've eagerly been following an upstream project's schedule, and
972when you check their homepage, guess what? They just released a new version a
973few minutes ago! Most users would immediately rush over to Gentoo's bugzilla to
974report the new version is available; please bump the existing version and add
975it to Portage, etc. However, this is exactly what you should <b>not</b> do.
976These kinds of requests are called zero-day (or 0-day) bump requests, as they're
977made the same day that a new version is released.
978</p>
979
980<impo>
981<b>Please wait <e>at least</e> 48 hours before reporting a new release on our
982bugzilla.</b> Also, you <e>must</e> check bugzilla before posting your request
983to make sure that someone else hasn't already reported it, or that the Gentoo
984maintainers haven't already dealt with the new version.
985</impo>
986
987<p>
988Why should you wait? First, it's quite rude to demand that Gentoo developers
989drop everything they're doing just to add a new release that came out 15 minutes
990ago. Your zero-day bump request could be marked as INVALID or LATER, as
991developers have plenty of pressing issues to keep them busy. Second, developers
992are usually aware of pending new releases well in advance of users, as they must
993follow upstream quite closely. They already know a new version is on its way.
994In many cases, they will have already opened a bug, or might even already added
995it in Portage as a masked package.
996</p>
997
998<p>
999Be smart when testing and requesting new versions of packages. Search bugzilla
1000before posting your bump request -- is there already a bug open? Have you synced
1001lately; is it already in Portage? Has it actually been released by upstream?
1002Basic common sense will go a long way, and will endear you to developers that
1003already have a lot to do. If it's been several days since release and you're
1004sure that there are no open requests for it (and that it's not in Portage), then
1005you can open up a new bug. Be sure to mention that it compiles and runs well on
1006your arch. Any other helpful information you provide is most welcome.
1007</p>
1008
1009<p>
1010Want to see the newest version of your favorite package in Portage? File smart
1011bugs.
1012</p>
1013
1014</body>
1015</section>
961</chapter> 1016</chapter>
962 1017
963<chapter> 1018<chapter>
964<title>Working With Your Bug</title> 1019<title>Working With Your Bug</title>
965<section> 1020<section>
966<body> 1021<body>
967 1022
968<p> 1023<p>
969Looking at the bug, we see the information we provided earlier. You will notice 1024Looking at the bug, we see the information we provided earlier. You will notice
970that the bug has been assigned to bug-wranglers@gentoo.org. This is the default 1025that the bug has been assigned to bug-wranglers@gentoo.org. This is the default
971location for Application component bugs. 1026location for Application component bugs.
972</p> 1027</p>
973 1028
974<figure link="/images/docs/bugzie-new-basic.png" caption="New Bug Basic Information"/> 1029<figure link="/images/docs/bugzie-new-basic.png" caption="New Bug Basic Information"/>
975 1030

Legend:
Removed from v.1.8  
changed lines
  Added in v.1.9

  ViewVC Help
Powered by ViewVC 1.1.20