[Piuparts-commits] [SCM] piatti.debian.org configuration files branch, master, updated. 0.42-38-g4d2c7ab

[Holger Levsen]

The following commit has been merged in the master branch:
commit 4d2c7abb7c5a5a8ae3a0e51c77b65c605e0eb457
Author: Holger Levsen <holger at layer-acht.org>
Date:   Sun Jan 22 12:24:53 2012 +0100

    improve bug-howto page and add news entry about it

diff --git a/org/piuparts.debian.org/htdocs/bug_howto.tpl b/org/piuparts.debian.org/htdocs/bug_howto.tpl
index 1a04194..9e7691c 100644
--- a/org/piuparts.debian.org/htdocs/bug_howto.tpl
+++ b/org/piuparts.debian.org/htdocs/bug_howto.tpl
@@ -6,22 +6,21 @@
     </tr>
     <tr class="normalrow">
      <td class="contentcell2">
-	This page shall grow into a well written explaination how to file useful bugs fast.
+	This page shall grow into a well written explaination how to file useful bugs fast. It assumes you are familar with <a href="http://www.debian.org/Bugs/Reporting" target="_blank">reporting bugs in Debian</a>.
      </td>
     </tr>
     <tr class="normalrow">
      <td class="contentcell2">
-	First, of all, read the piuparts logfile and identify why piuparts failed.
+	First, of all, read the piuparts logfile and identify why piuparts testing failed.
     </tr>
     <tr class="normalrow">
      <td class="contentcell2">
-	Then, check the BTS for that package, to see if this issue was already filedas a bug. Often it's also useful to check the source packages bug page.
-     </td>
+	Then, check the BTS for that package, to see if this issue was already filed as a bug. Often it's also useful to check the source packages bug page.
      </td>
     </tr>
     <tr class="normalrow">
      <td class="contentcell2">
-	Then, file a bug. The important thing here is to set a usertag like this:
+	Then, if there is none, file a bug. If there already is a bug describing the same problem you're seeing in the piuparts logfile, usertag it like this:
 	<pre>
  User: debian-qa at lists.debian.org
  Usertags: piuparts
@@ -32,7 +31,7 @@
     </tr>
     <tr class="normalrow">
      <td class="contentcell2">
-	The following is an example bug report. There are many more <a href="templates/mail/">templates</a> available for you to make use from!
+	Also, if you file a new bug report, don't forget to usertag it! The following is an example bug report. There are many more <a href="templates/mail/">templates</a> available for you to make use from!
 	<pre>
  To: submit at bugs.debian.org
  Subject: $package: fails to upgrade from 'testing' - trying to overwrite ...
@@ -67,6 +66,11 @@
     </tr>
     <tr class="normalrow">
      <td class="contentcell2">
+	Also, you should be aware that what you are doing can probably be seen as mass bug filing (even if you just file a few now, they are part of a series of bugs of one kind) and as such needs to be discussed on debian-devel at lists.d.o first! For many types of bugs this has already been done. This is or should be indicated in the summary web pages as well as the mail templates.
+     </td>
+    </tr>
+    <tr class="normalrow">
+     <td class="contentcell2">
 	Finally, besides simply usertagging a bug, piuparts-analyse understands more, and you can also do the following:
 	<pre>
  # assume 987654 is our bug report in buggy-package,
diff --git a/org/piuparts.debian.org/htdocs/index.tpl b/org/piuparts.debian.org/htdocs/index.tpl
index 719261a..818fc92 100644
--- a/org/piuparts.debian.org/htdocs/index.tpl
+++ b/org/piuparts.debian.org/htdocs/index.tpl
@@ -47,6 +47,11 @@
     </tr>
     <tr class="normalrow">
      <td class="contentcell2">
+      <b>2012-01-22</b>: Since some weeks, piuparts-analyse is captable of moving logfiles from fail to bugged, if there is a bug report usertagged 'piuparts' against that package+version combination. Thus, since today there is a webpage, explaining <a href="bug_howto.html">how to file bugs based on tests run on piuparts.debian.org</a>. So now the question how to help can easily be answered: read that page and start filing bugs!
+     </td>
+    </tr>
+    <tr class="normalrow">
+     <td class="contentcell2">
       <b>2012-01-20</b>: As squeeze2wheezy has been fully tested by today, re-enable rescheduling of old logs for sid, wheezy and squeezewheezy: 200 successful logs older than 90 days are rescheduled each day, plus 25 failed logs older than 30 days.
      </td>
     </tr>

-- 
piatti.debian.org configuration files