diff options
Diffstat (limited to 'zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217')
| -rw-r--r-- | zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment-0001.html | 177 | ||||
| -rw-r--r-- | zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment.html | 177 |
2 files changed, 354 insertions, 0 deletions
diff --git a/zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment-0001.html b/zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment-0001.html new file mode 100644 index 000000000..e6face780 --- /dev/null +++ b/zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment-0001.html @@ -0,0 +1,177 @@ +<html> + <head> + <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> + </head> + <body bgcolor="#FFFFFF" text="#000000"> + <pre>(Thanks Manuel, for improving what I wrote and thanks Dan for asking for examples.</pre> + <pre>I'll try to expand and improve this document - maybe even with screenshots - for use in the new wiki.)</pre> + <pre> +</pre> + <pre>Any suggestions (from anybody!) are welcome.</pre> + <pre> +But please don't look at the current triage guide now. +I don't want you to concentrate on that guide, but I would like you to concentrate on what you know or learned by experience. +Later on the triage guide can be compared with this document and they can be fused into a guide that contains the best of both <span class="moz-smiley-s1"><span> :-) </span></span></pre> + <pre> +</pre> + <pre>Op 28-09-11 00:33, Manuel Hiebel schreef:</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <pre wrap="">Le mardi 27 septembre 2011 à 23:08 +0200, Marja van Waes a écrit : +</pre> + <blockquote type="cite"> + <pre wrap=""> +</pre> + </blockquote> + </blockquote> + <pre> +</pre> + <pre><b>EASY THINGS TO BEGIN WITH: + +</b>PACKAGE REQUESTS: +</pre> + <pre> +</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <blockquote type="cite"> + <pre wrap="">Search bugzilla for package requests that haven't been assigned yet +<a class="moz-txt-link-freetext" href="https://bugs.mageia.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=REOPENED&component=New%20RPM%20package%20request">https://bugs.mageia.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=REOPENED&component=New%20RPM%20package%20request</a> + +Some requesters forget to give a link to where the software can be +found. </pre> + </blockquote> + </blockquote> + <pre> + +</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <pre> + </pre> + <blockquote type="cite"> + <pre wrap="">If they haven't given a link at all, you can ask them to give the +upstream link to the package. If they say: it is a Mandriva package, +you can say: not all our packagers are familiar with Mandriva, so +please give an upstream link. +</pre> + </blockquote> + <pre> +</pre> + </blockquote> + <pre> +</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <blockquote type="cite"> + <pre wrap="">Or they put the link in the description field, which is good, +but the <u>link should also go in the URL field</u>. Like +<a class="moz-txt-link-freetext" href="https://bugs.mageia.org/show_bug.cgi?id=1067">https://bugs.mageia.org/show_bug.cgi?id=1067</a> You can copy the link to +the url field, if you want to +</pre> + </blockquote> + <pre wrap=""> +You can also <u>complete the field RPM package</u>, and make an precise summary +if that is not enough (like removing: "I'd like to see this package in +mageia" </pre> + </blockquote> + <pre>and replace it</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <pre wrap=""><u>with "$name-of-the-package, $a very short description"</u></pre> + </blockquote> + <pre> +</pre> + <pre>BUGS: + +Not all steps ar easy, you can start doing what is easy for you and leave the rest to others. +No bugs should be assigned to a maintainer before all necessary steps are taken (unless, of course, the maintainer chooses to grab the bug) + + +Step 1 + + +</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <blockquote type="cite"> + <pre wrap=""> +Look at the +new bugs that are reported and use bugzilla to find out whether one is +a <u>duplicate</u> of an existing bug. If you are not used to searching +bugzilla: play around with it first. And don't forget to try the +advanced options <a class="moz-txt-link-freetext" href="https://bugs.mageia.org/query.cgi">https://bugs.mageia.org/query.cgi</a> (choose right tab: +advanced search) +</pre> + </blockquote> + </blockquote> + <pre>Step 2a + +Dit the reporter give the needed basic information about the Mageia release he uses and what steps to take to reproduce the bug? + +ADD:(examples of reports with and without needed info) + + +step 2b (often not so easy, if you don't know how to do it: leave it to others and watch what they do) + +Check wether the reporter gave needed backtraces, if he didn't: ask for them and tell him how to get them if he doesn't know + +ADD: (examples) + + +Step 3 + +</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <blockquote type="cite"> + <pre wrap=""> +If someone has the same version of Mandriva as you and reports a bug +in a program you are familiar with, you can try to <u>reproduce</u> the bug. + + +</pre> + </blockquote> + </blockquote> + <pre>But often other Mageia users report that they have the same bug, so then they reproduced it.</pre> + <pre>If it can't be reproduced, than it isn't a bug and the bug should be closed +(but please tell the user he can find help for his problem on <a class="moz-txt-link-freetext" href="https://forums.mageia.org/en/">https://forums.mageia.org/en/</a>)</pre> + <pre> +Step 4 + +</pre> + <pre> +</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <pre wrap=""> +You can also <u>add a maintainer</u> like what I do here: +<a class="moz-txt-link-freetext" href="https://bugs.mageia.org/show_bug.cgi?id=2856">https://bugs.mageia.org/show_bug.cgi?id=2856</a> + +<a class="moz-txt-link-freetext" href="https://bugs.mageia.org/show_activity.cgi?id=2856">https://bugs.mageia.org/show_activity.cgi?id=2856</a> + +check the src.rpm: + :src claws-mail with sophie (on irc or sophie.zarb.org) +or urpmq --sourcerpm claws-mail + +then search the maintainer: + :maint claws-mail +or search on the txt list: <a class="moz-txt-link-freetext" href="http://pkgsubmit.mageia.org/data/maintdb.txt">http://pkgsubmit.mageia.org/data/maintdb.txt</a> + +then search the email of the maintainer: julien on the page +<a class="moz-txt-link-freetext" href="http://www.mageia.org/wiki/doku.php?id=packaging#list_of_registered_people">http://www.mageia.org/wiki/doku.php?id=packaging#list_of_registered_people</a> + +or just type the id, sometime it's work (like for misc, tmb,...), +sometimes not (like here, there is two id) :) +</pre> + </blockquote> + <pre>OLD BUGS: +</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <pre wrap=""> +We must check that for all 'old' bug. +Here is a saved-search for all bug assigned to bugsquad: +<a class="moz-txt-link-freetext" href="https://bugs.mageia.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Bugs%20not%20triaged%20%28excl%20new%20RPM%20requests%29&sharer_id=35">https://bugs.mageia.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Bugs%20not%20triaged%20%28excl%20new%20RPM%20requests%29&sharer_id=35</a> + +</pre> + </blockquote> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <pre> +</pre> + </blockquote> + <pre> +</pre> + </body> +</html> diff --git a/zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment.html b/zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment.html new file mode 100644 index 000000000..e6face780 --- /dev/null +++ b/zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment.html @@ -0,0 +1,177 @@ +<html> + <head> + <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> + </head> + <body bgcolor="#FFFFFF" text="#000000"> + <pre>(Thanks Manuel, for improving what I wrote and thanks Dan for asking for examples.</pre> + <pre>I'll try to expand and improve this document - maybe even with screenshots - for use in the new wiki.)</pre> + <pre> +</pre> + <pre>Any suggestions (from anybody!) are welcome.</pre> + <pre> +But please don't look at the current triage guide now. +I don't want you to concentrate on that guide, but I would like you to concentrate on what you know or learned by experience. +Later on the triage guide can be compared with this document and they can be fused into a guide that contains the best of both <span class="moz-smiley-s1"><span> :-) </span></span></pre> + <pre> +</pre> + <pre>Op 28-09-11 00:33, Manuel Hiebel schreef:</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <pre wrap="">Le mardi 27 septembre 2011 à 23:08 +0200, Marja van Waes a écrit : +</pre> + <blockquote type="cite"> + <pre wrap=""> +</pre> + </blockquote> + </blockquote> + <pre> +</pre> + <pre><b>EASY THINGS TO BEGIN WITH: + +</b>PACKAGE REQUESTS: +</pre> + <pre> +</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <blockquote type="cite"> + <pre wrap="">Search bugzilla for package requests that haven't been assigned yet +<a class="moz-txt-link-freetext" href="https://bugs.mageia.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=REOPENED&component=New%20RPM%20package%20request">https://bugs.mageia.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=REOPENED&component=New%20RPM%20package%20request</a> + +Some requesters forget to give a link to where the software can be +found. </pre> + </blockquote> + </blockquote> + <pre> + +</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <pre> + </pre> + <blockquote type="cite"> + <pre wrap="">If they haven't given a link at all, you can ask them to give the +upstream link to the package. If they say: it is a Mandriva package, +you can say: not all our packagers are familiar with Mandriva, so +please give an upstream link. +</pre> + </blockquote> + <pre> +</pre> + </blockquote> + <pre> +</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <blockquote type="cite"> + <pre wrap="">Or they put the link in the description field, which is good, +but the <u>link should also go in the URL field</u>. Like +<a class="moz-txt-link-freetext" href="https://bugs.mageia.org/show_bug.cgi?id=1067">https://bugs.mageia.org/show_bug.cgi?id=1067</a> You can copy the link to +the url field, if you want to +</pre> + </blockquote> + <pre wrap=""> +You can also <u>complete the field RPM package</u>, and make an precise summary +if that is not enough (like removing: "I'd like to see this package in +mageia" </pre> + </blockquote> + <pre>and replace it</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <pre wrap=""><u>with "$name-of-the-package, $a very short description"</u></pre> + </blockquote> + <pre> +</pre> + <pre>BUGS: + +Not all steps ar easy, you can start doing what is easy for you and leave the rest to others. +No bugs should be assigned to a maintainer before all necessary steps are taken (unless, of course, the maintainer chooses to grab the bug) + + +Step 1 + + +</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <blockquote type="cite"> + <pre wrap=""> +Look at the +new bugs that are reported and use bugzilla to find out whether one is +a <u>duplicate</u> of an existing bug. If you are not used to searching +bugzilla: play around with it first. And don't forget to try the +advanced options <a class="moz-txt-link-freetext" href="https://bugs.mageia.org/query.cgi">https://bugs.mageia.org/query.cgi</a> (choose right tab: +advanced search) +</pre> + </blockquote> + </blockquote> + <pre>Step 2a + +Dit the reporter give the needed basic information about the Mageia release he uses and what steps to take to reproduce the bug? + +ADD:(examples of reports with and without needed info) + + +step 2b (often not so easy, if you don't know how to do it: leave it to others and watch what they do) + +Check wether the reporter gave needed backtraces, if he didn't: ask for them and tell him how to get them if he doesn't know + +ADD: (examples) + + +Step 3 + +</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <blockquote type="cite"> + <pre wrap=""> +If someone has the same version of Mandriva as you and reports a bug +in a program you are familiar with, you can try to <u>reproduce</u> the bug. + + +</pre> + </blockquote> + </blockquote> + <pre>But often other Mageia users report that they have the same bug, so then they reproduced it.</pre> + <pre>If it can't be reproduced, than it isn't a bug and the bug should be closed +(but please tell the user he can find help for his problem on <a class="moz-txt-link-freetext" href="https://forums.mageia.org/en/">https://forums.mageia.org/en/</a>)</pre> + <pre> +Step 4 + +</pre> + <pre> +</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <pre wrap=""> +You can also <u>add a maintainer</u> like what I do here: +<a class="moz-txt-link-freetext" href="https://bugs.mageia.org/show_bug.cgi?id=2856">https://bugs.mageia.org/show_bug.cgi?id=2856</a> + +<a class="moz-txt-link-freetext" href="https://bugs.mageia.org/show_activity.cgi?id=2856">https://bugs.mageia.org/show_activity.cgi?id=2856</a> + +check the src.rpm: + :src claws-mail with sophie (on irc or sophie.zarb.org) +or urpmq --sourcerpm claws-mail + +then search the maintainer: + :maint claws-mail +or search on the txt list: <a class="moz-txt-link-freetext" href="http://pkgsubmit.mageia.org/data/maintdb.txt">http://pkgsubmit.mageia.org/data/maintdb.txt</a> + +then search the email of the maintainer: julien on the page +<a class="moz-txt-link-freetext" href="http://www.mageia.org/wiki/doku.php?id=packaging#list_of_registered_people">http://www.mageia.org/wiki/doku.php?id=packaging#list_of_registered_people</a> + +or just type the id, sometime it's work (like for misc, tmb,...), +sometimes not (like here, there is two id) :) +</pre> + </blockquote> + <pre>OLD BUGS: +</pre> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <pre wrap=""> +We must check that for all 'old' bug. +Here is a saved-search for all bug assigned to bugsquad: +<a class="moz-txt-link-freetext" href="https://bugs.mageia.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Bugs%20not%20triaged%20%28excl%20new%20RPM%20requests%29&sharer_id=35">https://bugs.mageia.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Bugs%20not%20triaged%20%28excl%20new%20RPM%20requests%29&sharer_id=35</a> + +</pre> + </blockquote> + <blockquote cite="mid:1317162819.27225.17.camel@vosdook" type="cite"> + <pre> +</pre> + </blockquote> + <pre> +</pre> + </body> +</html> |