| 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"> |
| … | |
… | |
| 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> |
| … | |
… | |
| 956 | with. |
956 | with. |
| 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> |
|
|
966 | So 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> |
|
|
971 | Suppose that you've eagerly been following an upstream project's schedule, and |
|
|
972 | when you check their homepage, guess what? They just released a new version a |
|
|
973 | few minutes ago! Most users would immediately rush over to Gentoo's bugzilla to |
|
|
974 | report the new version is available; please bump the existing version and add |
|
|
975 | it to Portage, etc. However, this is exactly what you should <b>not</b> do. |
|
|
976 | These kinds of requests are called zero-day (or 0-day) bump requests, as they're |
|
|
977 | made 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 |
|
|
982 | bugzilla.</b> Also, you <e>must</e> check bugzilla before posting your request |
|
|
983 | to make sure that someone else hasn't already reported it, or that the Gentoo |
|
|
984 | maintainers haven't already dealt with the new version. |
|
|
985 | </impo> |
|
|
986 | |
|
|
987 | <p> |
|
|
988 | Why should you wait? First, it's quite rude to demand that Gentoo developers |
|
|
989 | drop everything they're doing just to add a new release that came out 15 minutes |
|
|
990 | ago. Your zero-day bump request could be marked as INVALID or LATER, as |
|
|
991 | developers have plenty of pressing issues to keep them busy. Second, developers |
|
|
992 | are usually aware of pending new releases well in advance of users, as they must |
|
|
993 | follow upstream quite closely. They already know a new version is on its way. |
|
|
994 | In many cases, they will have already opened a bug, or might even already added |
|
|
995 | it in Portage as a masked package. |
|
|
996 | </p> |
|
|
997 | |
|
|
998 | <p> |
|
|
999 | Be smart when testing and requesting new versions of packages. Search bugzilla |
|
|
1000 | before posting your bump request -- is there already a bug open? Have you synced |
|
|
1001 | lately; is it already in Portage? Has it actually been released by upstream? |
|
|
1002 | Basic common sense will go a long way, and will endear you to developers that |
|
|
1003 | already have a lot to do. If it's been several days since release and you're |
|
|
1004 | sure that there are no open requests for it (and that it's not in Portage), then |
|
|
1005 | you can open up a new bug. Be sure to mention that it compiles and runs well on |
|
|
1006 | your arch. Any other helpful information you provide is most welcome. |
|
|
1007 | </p> |
|
|
1008 | |
|
|
1009 | <p> |
|
|
1010 | Want to see the newest version of your favorite package in Portage? File smart |
|
|
1011 | bugs. |
|
|
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> |
Parent Directory
| 
Revision Log
| 
Patch