| 1 |
jer 08/09/08 16:24:09 |
| 2 |
|
| 3 |
Modified: index.xml |
| 4 |
Log: |
| 5 |
Clarify KEYWORDREQ. Explain more about eclass bug assignment. Stress atom description in Summary. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.8 xml/htdocs/proj/en/qa/bug-wranglers/index.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.8&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.8&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.7&r2=1.8 |
| 13 |
|
| 14 |
Index: index.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v |
| 17 |
retrieving revision 1.7 |
| 18 |
retrieving revision 1.8 |
| 19 |
diff -u -r1.7 -r1.8 |
| 20 |
--- index.xml 2 Sep 2008 20:35:44 -0000 1.7 |
| 21 |
+++ index.xml 8 Sep 2008 16:24:08 -0000 1.8 |
| 22 |
@@ -6,7 +6,7 @@ |
| 23 |
<project> |
| 24 |
<name>Bug Wranglers</name> |
| 25 |
<longname>The Bug Wranglers Project</longname> |
| 26 |
-<date>2008-09-02</date> |
| 27 |
+<date>2008-09-08</date> |
| 28 |
<author title="Author"> |
| 29 |
<mail link="jer" /> |
| 30 |
</author> |
| 31 |
@@ -80,8 +80,11 @@ |
| 32 |
with a more exact description, noting the ebuild phase that failed or, better |
| 33 |
yet, the first error message that occured.</li> |
| 34 |
<li>Bug reports that refer to a single or a few (similar) packages should |
| 35 |
-detail the package atom as completely as possible in the <c>Summary</c>. Bug reports |
| 36 |
-about eclasses should list the full eclass filename.</li> |
| 37 |
+detail the <b>package atom(s)</b> as completely as possible in the |
| 38 |
+<c>Summary</c>, including a version only when other versions do not exhibit the |
| 39 |
+bug.</li> |
| 40 |
+<li>Bug reports about <b>eclasses</b> should list the full eclass filename in the |
| 41 |
+<c>Summary</c>.</li> |
| 42 |
</ul> |
| 43 |
</body> |
| 44 |
</section> |
| 45 |
@@ -123,11 +126,16 @@ |
| 46 |
<li>Bug reports that concern <b>eclasses</b> should be assigned to the eclass |
| 47 |
maintainer. To figure out who maintains an eclass, browse to the |
| 48 |
<uri link="http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass">gentoo-x86/eclass</uri> |
| 49 |
-directory, open the file and read who maintains the eclass at the top of the file.</li> |
| 50 |
-<li>A <b>keyword request</b> should be assigned to the package's maintainer and CC'd |
| 51 |
-to the appropriate arch team(s).</li> |
| 52 |
+directory, open the file and read who maintains the eclass at the top of the |
| 53 |
+file. When an eclass file does not list maintainers, the bug report should |
| 54 |
+note this omission and the last committer to that file should be made the |
| 55 |
+report's assignee.</li> |
| 56 |
+<li>A <b>keyword request</b> should be assigned to the package's maintainer and |
| 57 |
+CC'd to the appropriate arch team(s). The report's <c>Keywords</c> field should |
| 58 |
+contain the <c>KEYWORDREQ</c> keyword.</li> |
| 59 |
<li>A <b>stabilisation request</b> should be handled by the package's maintainer, so |
| 60 |
-you should not CC arches in your role as bug wrangler.</li> |
| 61 |
+you should not CC arch teams in your role as bug wrangler, nor set the |
| 62 |
+<c>STABLEREQ</c> keyword in the <c>Keywords</c> field.</li> |
| 63 |
<li>Bug reports that relate to issues other than the portage tree, like |
| 64 |
problems with Gentoo's bugzilla, Gentoo infrastructure, mirrors or staffing |
| 65 |
matters (devrel, userrel and so on) are usually easier to assign. The <c>Product</c> |
Archives