| 1 |
nightmorph 07/02/14 21:30:16 |
| 2 |
|
| 3 |
Modified: bugzilla-howto.xml |
| 4 |
Log: |
| 5 |
added a section on zero-day bump requests to the bugzilla guide for bug 166809 |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.9 xml/htdocs/doc/en/bugzilla-howto.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.9&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.9&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?r1=1.8&r2=1.9 |
| 13 |
|
| 14 |
Index: bugzilla-howto.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v |
| 17 |
retrieving revision 1.8 |
| 18 |
retrieving revision 1.9 |
| 19 |
diff -u -r1.8 -r1.9 |
| 20 |
--- bugzilla-howto.xml 10 Nov 2006 22:19:40 -0000 1.8 |
| 21 |
+++ bugzilla-howto.xml 14 Feb 2007 21:30:15 -0000 1.9 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.8 2006/11/10 22:19:40 nightmorph Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.9 2007/02/14 21:30:15 nightmorph Exp $ --> |
| 27 |
|
| 28 |
<guide link="/doc/en/bugzilla-howto.xml"> |
| 29 |
<title>Gentoo Bug Reporting Guide</title> |
| 30 |
@@ -20,8 +20,8 @@ |
| 31 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 32 |
<license/> |
| 33 |
|
| 34 |
-<version>1.7</version> |
| 35 |
-<date>2006-11-10</date> |
| 36 |
+<version>1.8</version> |
| 37 |
+<date>2007-02-14</date> |
| 38 |
|
| 39 |
<chapter> |
| 40 |
<title>Introduction</title> |
| 41 |
@@ -958,6 +958,61 @@ |
| 42 |
|
| 43 |
</body> |
| 44 |
</section> |
| 45 |
+<section> |
| 46 |
+<title>Zero-day bump requests</title> |
| 47 |
+<body> |
| 48 |
+ |
| 49 |
+<p> |
| 50 |
+So far, we've shown what to do when filing a bug. Now let's take a look at what |
| 51 |
+<e>not</e> to do. |
| 52 |
+</p> |
| 53 |
+ |
| 54 |
+<p> |
| 55 |
+Suppose that you've eagerly been following an upstream project's schedule, and |
| 56 |
+when you check their homepage, guess what? They just released a new version a |
| 57 |
+few minutes ago! Most users would immediately rush over to Gentoo's bugzilla to |
| 58 |
+report the new version is available; please bump the existing version and add |
| 59 |
+it to Portage, etc. However, this is exactly what you should <b>not</b> do. |
| 60 |
+These kinds of requests are called zero-day (or 0-day) bump requests, as they're |
| 61 |
+made the same day that a new version is released. |
| 62 |
+</p> |
| 63 |
+ |
| 64 |
+<impo> |
| 65 |
+<b>Please wait <e>at least</e> 48 hours before reporting a new release on our |
| 66 |
+bugzilla.</b> Also, you <e>must</e> check bugzilla before posting your request |
| 67 |
+to make sure that someone else hasn't already reported it, or that the Gentoo |
| 68 |
+maintainers haven't already dealt with the new version. |
| 69 |
+</impo> |
| 70 |
+ |
| 71 |
+<p> |
| 72 |
+Why should you wait? First, it's quite rude to demand that Gentoo developers |
| 73 |
+drop everything they're doing just to add a new release that came out 15 minutes |
| 74 |
+ago. Your zero-day bump request could be marked as INVALID or LATER, as |
| 75 |
+developers have plenty of pressing issues to keep them busy. Second, developers |
| 76 |
+are usually aware of pending new releases well in advance of users, as they must |
| 77 |
+follow upstream quite closely. They already know a new version is on its way. |
| 78 |
+In many cases, they will have already opened a bug, or might even already added |
| 79 |
+it in Portage as a masked package. |
| 80 |
+</p> |
| 81 |
+ |
| 82 |
+<p> |
| 83 |
+Be smart when testing and requesting new versions of packages. Search bugzilla |
| 84 |
+before posting your bump request -- is there already a bug open? Have you synced |
| 85 |
+lately; is it already in Portage? Has it actually been released by upstream? |
| 86 |
+Basic common sense will go a long way, and will endear you to developers that |
| 87 |
+already have a lot to do. If it's been several days since release and you're |
| 88 |
+sure that there are no open requests for it (and that it's not in Portage), then |
| 89 |
+you can open up a new bug. Be sure to mention that it compiles and runs well on |
| 90 |
+your arch. Any other helpful information you provide is most welcome. |
| 91 |
+</p> |
| 92 |
+ |
| 93 |
+<p> |
| 94 |
+Want to see the newest version of your favorite package in Portage? File smart |
| 95 |
+bugs. |
| 96 |
+</p> |
| 97 |
+ |
| 98 |
+</body> |
| 99 |
+</section> |
| 100 |
</chapter> |
| 101 |
|
| 102 |
<chapter> |
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
-- |
| 107 |
gentoo-doc-cvs@g.o mailing list |
Archives