rev 5040 - www/v2/pages
Sune Vuorela
pusling-guest at alioth.debian.org
Sun Dec 3 16:53:42 CET 2006
Author: pusling-guest
Date: 2006-12-03 16:53:41 +0100 (Sun, 03 Dec 2006)
New Revision: 5040
Added:
www/v2/pages/bugs
www/v2/pages/kde-bugzilla-survival-guide
www/v2/pages/usertags
Modified:
www/v2/pages/bottom
Log:
Adding pages - breakin the designs
Modified: www/v2/pages/bottom
===================================================================
--- www/v2/pages/bottom 2006-12-03 11:31:10 UTC (rev 5039)
+++ www/v2/pages/bottom 2006-12-03 15:53:41 UTC (rev 5040)
@@ -6,6 +6,10 @@
<ul>
<li><a href="qtkde.html">General info</a></li>
<li><a href="http://qa.debian.org/developer.php?login=debian-qt-kde@lists.debian.org">Package list</a></li>
+ <li><a href="bugs.html">Handle and search bugs</a>
+ <ul>
+ <li><a href="usertags.html">Use of usertags</a></li>
+ </ul></li>
</ul>
<h2>Debian KDE Extras Team</h2>
@@ -21,6 +25,7 @@
<li><a href="kde4.html">KDE4</a></li>
<li><a href="descriptions.html">Descriptions policy draft</a></li>
<li><a href="btslink.html">bts-link</a></li>
+ <li><a href="kde-bugzilla-survival-guide.html">Survival guide to kde bugzilla</a></li>
<li><a href="#">How to package kde applications</a></li>
<li><a href="#">SVN quick guide</a></li>
Added: www/v2/pages/bugs
===================================================================
--- www/v2/pages/bugs 2006-12-03 11:31:10 UTC (rev 5039)
+++ www/v2/pages/bugs 2006-12-03 15:53:41 UTC (rev 5040)
@@ -0,0 +1,129 @@
+<h2>Bug triaging</h2>
+<p>
+The following strategy is the one mostly used on bug triaging among the kde packagers:<br />
+</p>
+<ul>
+<li>Try to reproduce. Don't use more than 5 minutes in trying to understand what submitter means</li>
+<li>If it is reproducible, fix it in the kde packaging, if it is packaging bug. Report it upstream if it is upstream bug. Write a patch if it is appropriate.</li>
+<li>If it is unreproducible, ask the submitter for more info about how to reproduce and a step by step guide. Tag the bug unreproducible and moreinfo</li>
+<li>If it contains a useless backtrace, ask submitter to provide a better backtrace by installing relevant -dbg packages</li>
+<li>Wait for submitter to reply. Repeat the last steps with submitter until it is clear and reproducible</li>
+<li>If no response from submitter, close the bug after approx. 4 weeks</li>
+</ul>
+<p>
+Some of the importaint steps was 1) remember to tag +moreinfo unreproducible when asking for moreinfo and remember to mark the bug as forwarded.
+</p>
+<h3>Bug tagging and forwarding</h3>
+<p>
+Bug tagging is done by mails to control. When a comment is needed, it can be in the same mail, just remember to email the right people. The following is a example of a mail describing who to mail (the 3 To: lines) and the content of the mail (The rest of the mail starting from tag)
+</p>
+<pre>
+To: 1234-submitter at bugs.debian.org
+To: 1234 at bugs.debian.org
+To: control at bugs.debian.org
+
+tag 1234 +moreinfo unreproducible
+thanks
+
+Hi!
+I have tried to reproduce your bug with the help of your instructions.
+I am unfortunately not able to reproduce it. Does it still apply? If yes,
+please provide detailed steps on how to reproduce.
+
+/Sune
+</pre>
+<p>
+Someones from the kde team will try to go over the moreinfo bugs regularily and either close them or remove the moreinfo-tag
+</p>
+<h3>Closing bugs</h3>
+<p>
+A bug is normally versioned closed. That way, the bugs can be tracked thru the different distributions. It is importaint that the version a bug is closed in is a version that has existed in debian.<br />
+Moreinfo-bugs are closed after 4 weeks with out more info from submitter. The list of bugs tagged moreinfo is <a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=debian-qt-kde@lists.debian.org;dist=unstable;include=moreinfo;pend-exc=done;pend-exc=forwarded">here</a><br />
+A bug is closed by a mail to nnn-done at bugs.debian.org with Version: 4:1.3.4-6 as first line. Then a empty line and finally a explanation why the bug is closed.<br />
+Like this
+</p>
+<pre>
+To: 1234-done at bugs.debian.org
+
+Version: 4:3.5.0-3
+
+This bug is fixed half year ago upstream in http://bugs.upstream/37489
+The fix have made debian long time ago. Closing this bug.
+
+/Sune
+</pre>
+<p>
+Happy bug closing!
+</p>
+
+<h2>Links to bts</h2>
+<p>
+This is a attempt to try to group the bugs in sections of relevance - or just in smaller sections.
+A package like konqueror has many different functions and not all people use all of these functions.
+</p>
+<p>
+Some links are to source packages, other pages are to binary packages and then again some to only parts of a binary package.
+</p>
+<p>
+The third level is manually tagged so it might be inaccurate.
+</p>
+<p>
+<a href="usertags.html">For more on bug tagging</a> and <a href="usertags.html#used">for used usertags in kde packages</a> there are special pages available
+</p>
+<ul>
+ <li><a href="http://bugs.debian.org/src:kdepim">Bugs in kdepim</a>
+ <ul>
+ <li><a href="http://bugs.debian.org/kmail">Bugs in kmail</a>
+ <ul>
+ <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-kde@lists.debian.org;tag=kmail-imap;dist=unstable">Imap-related bugs in kmail</a></li>
+ <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=kmail;users=debian-qt-kde@lists.debian.org;exclude=kmail-imap;dist=unstable">All other kmail bugs</a></li>
+ </ul>
+ </li>
+ <li><a href="http://bugs.debian.org/kontact">Bugs in kontact</a></li>
+ <li><a href="http://bugs.debian.org/kpilot">Bugs in kpilot</a></li>
+
+
+
+ </ul>
+ </li>
+ <li><a href="http://bugs.debian.org/src:kdebase">Bugs in kdebase</a>
+ <ul>
+ <li><a href="http://bugs.debian.org/konqueror">Bugs in konqueror</a>
+ <ul>
+ <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-kde@lists.debian.org;tag=konqeror-filemanager;dist=unstable">Konqueror as file manager</a></li>
+ <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-kde@lists.debian.org;tag=konqeror-webbrowser;dist=unstable">Konqueror as webbrowser</a></li>
+ <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=konqueror;users=debian-qt-kde@lists.debian.org;exclude=konqueror-filemanager;exclude=konqueror-webbrowser;dist=unstable">All other bugs in konqueror</a></li>
+ </ul>
+ </li>
+ <li><a href="http://bugs.debian.org/kdm">bugs in kdm</a></li>
+ </ul>
+ </li>
+ <li><a href="http://bugs.debian.org/src:kdenetwork">Bugs in kdenetwork</a>
+ <ul>
+ <li><a href="http://bugs.debian.org/kopete">Bugs in kopete</a>
+ <ul>
+ <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-kde@lists.debian.org;tag=kopete-msn;dist=unstable">Bugs related to kopete as msn cliens</a></li>
+ <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-kde@lists.debian.org;tag=kopete-icq;dist=unstable">Bugs related to kopete as icq cliens</a></li>
+ <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-kde@lists.debian.org;tag=kopete-irc;dist=unstable">Bugs related to kopete as irc cliens</a></li>
+ <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=kopete;users=debian-qt-kde@lists.debian.org;exclude=kopete-msn;exclude=kopete-irc;exclude=kopete-icq;dist=unstable">Other kopete bugs</a></li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+</ul>
+
+<h3>Other categories</h3>
+<p>
+Some bugs needs something special to be reproduced (and fixed). These are tagged manually as well.
+</p>
+<ul>
+ <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-kde@lists.debian.org;tag=kde-needs-ldap;dist=unstable">Needs somekind of interaction with ldap server</a></li>
+ <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-kde@lists.debian.org;tag=kde-needs-exchange;dist=unstable">Interaction with exchange-server</a></li>
+ <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-kde@lists.debian.org;tag=kde-needs-home-on-nfs;dist=unstable">Needs home on nfs or other network file systems</a></li>
+ <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-kde@lists.debian.org;tag=kde-fancy-x;dist=unstable">Needs fancy X-settings (trancluciency, composite and similar)</a></li>
+
+
+
+</ul>
+</body>
+</html>
Added: www/v2/pages/kde-bugzilla-survival-guide
===================================================================
--- www/v2/pages/kde-bugzilla-survival-guide 2006-12-03 11:31:10 UTC (rev 5039)
+++ www/v2/pages/kde-bugzilla-survival-guide 2006-12-03 15:53:41 UTC (rev 5040)
@@ -0,0 +1,18 @@
+<h2>Survival guide to the kde bugzilla</h2>
+<p>
+Many of the kde packages fear the kde bugzilla, mostly because it is quite easy to get lost and really hard to find the right bugs in the right packages. Very often, you are met by the phrase <em>zarro boogs found</em> or alternatively you get too many bug reports.</p>
+<p>
+Starting the search from the right pages might help a bit, but very often, creating hand-crafted urls actually is the fastest. In the following parts, it will be described where to start and a couple of hand crafted urls will also be shown</p>
+<h3>Starting in kde bugzilla</h3>
+The offical entrance is at <a href="http://bugs.kde.org">http://bugs.kde.org</a> and here is a lot of links to different places. The most useful search page is the <a href="http://bugs.kde.org/query.cgi">Query reports (complex)</a> page. It gives a lot of possibilities to make different searches.<br />
+On newly reported rc bugs, the two pages with the newly reported bugs in kde might also be of some kind of help. This is the bugs opened today and the bugs opened within the last 3 days. Doing deep linking to those is not easy, as the links are dynamically generated.<br />
+<h3>Handcrafting urls</h3>
+<p>
+By looking on the url generated by the <a href="http://bugs.kde.org/query.cgi">Query reports (complex)</a> page, it is often both faster and easier to just change the url instead of creating a entire new search.<br />
+For example, this url http://bugs.kde.org/buglist.cgi?product=<strong>kcontrol</strong>&component=<strong>kcmaccessibility</strong>&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=CLOSED shows all open bugs and all resolved bugs in the kcmaccessibility module of kcontrol. To only show the open bugs, just remove the &bug_status=RESOLVED&bug_status=CLOSED from the url.<br />
+And the following url shows all bugs in kgpg product: http://bugs.kde.org/buglist.cgi?product=<strong>kgpg</strong>&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=CLOSED<br />
+Searching can also often be interesting. The following url is good to use for searching: http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=<strong>UTF8</strong>&long_desc_type=allwordssubstr&long_desc=&product=<strong>konsole</strong>&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=CLOSED&order=Reuse+same+sort+as+last+time&cmdtype=doit which is all bugs about the string "utf8" in konsole
+</p>
+<p>
+The easiest thing is often to create a appropriate query that gives 100-200 results and quick read thru the bug titles.
+</p>
Added: www/v2/pages/usertags
===================================================================
--- www/v2/pages/usertags 2006-12-03 11:31:10 UTC (rev 5039)
+++ www/v2/pages/usertags 2006-12-03 15:53:41 UTC (rev 5040)
@@ -0,0 +1,86 @@
+<html><head><title></title></head><body>
+<h2>Usertags</h2>
+<p>
+Usertags is a new nice feature in the bug tracking system that can be used to tag bugs how you like to do it.
+The tags are bound to a user, and a user is in this case a email address. Usertags can be used to create different views on bugs and it can also be used to track stuff across packages.
+</p>
+<p>
+The kde packagers mostly use the tags associated with debian-qt-kde at lists.debian.org to create views of related bugs or bugs with special needs. The special views are for larger programs like konqueror that have many different functions to show bugs only for one of the tasks. The special needs could be that the bug is relatet to interaction with a Microsoft Exchange server.
+</p>
+<h3>How to set usertags</h3>
+<p>
+Usertags are set by emails to control at bugs.debian.org just like ordinary tags. The syntax is a bit different and there is not a predefined set of tags, so beware of typos.</p>
+<pre>
+user debian-qt-kde at lists.debian.org
+usertag #1234 +kde-foo
+</pre>
+<p>Please only set the predefined tags already used by the kde packagers. If you find a need for a new tag, please approach the packagers before using it, or alternatively tag bugs as your own user.
+</p>
+
+<h3>How to view usertags</h3>
+<p>The usertags are viewed by handcrafting urls to the bug system, more specifically adding arguments to pkgreport.cgi. The different arguments are seperated by semicolon (;).<br />The following arguments are recognized</p>
+<dl>
+ <dt>pkg</dt>
+ <dd>include all bugs by binary package</dd>
+ <dt>src</dt>
+ <dd>include all bugs by source package</dd>
+ <dt>maint</dt>
+ <dd>include all bugs by package maintainer (email address)</dd>
+ <dt>dist</dt>
+ <dd>include bugs that applies to distribution (stable, testing, unstable)</dd>
+ <dt>users</dt>
+ <dd>Set the user for usertags. Multiple users can be seperated with colon (:)</dd>
+ <dt>tag</dt>
+ <dd>include bugs with the following tags. Can be specified multiple times or alternatively tags can be comma (,) seperated</dd>
+ <dt>exclude</dt>
+ <dd>exclude bugs with the following tags. Can be specified multiple times or alternatively tags can be comma (,) seperated</dd>
+</dl>
+<p>
+With these arguments, most views are created. A couple of examples:
+</p>
+<dl>
+ <dt>http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-kde@lists.debian.org;tag=kmail-imap;dist=unstable</dt>
+ <dd>Bugs in unstable tagged kmail-imap by the user debian-qt-kde at lists.debian.org</dd>
+ <dt>http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=konqueror;users=debian-qt-kde@lists.debian.org;exclude=konqueror-filemanager;exclude=konqueror-webbrowser;dist=unstable</dt>
+ <dd>Bugs in unstable in binary package konqueror not tagged konqueror-filemanegor or konqueror-webbrowser by the user debian-qt-kde at lists.debian.org</dd>
+</dl>
+
+
+<h3><a name="used" />The usertags used by the kde packagers</h3>
+<p>Some usertags are in the kde packages only used in specific source packages. Other usertags are used across all source packages.</p>
+<h4>kdepim</h4>
+<dl>
+ <dt>kmail-imap</dt>
+ <dd>Imap-related bugs in konqueror</dd>
+ <dt>kmail-ssl</dt>
+ <dd>bugs in kmail related to ssl-connections</dd>
+</dl>
+<h4>kdebase</h4>
+<dl>
+ <dt>konqueror-webbrowser</dt>
+ <dd>Bugs in konqueror as browser on world wide web. Mostly crashes on webpages and bad rendering</dd>
+ <dt>konqueror-filemanager</dt>
+ <dd>Bugs in konqueror related to its use as a filemanager</dd>
+</dl>
+<h4>kdenetwork</h4>
+<dl>
+ <dt>kopete-msn</dt>
+ <dd>kopete as a client for msn network</dd>
+ <dt>kopete-icq</dt>
+ <dd>kopete as a icq client</dd>
+ <dt>kopete-irc</dt>
+ <dd>kopete as irc client</dd>
+</dl>
+<h4>Tags across source packages</h4>
+<dl>
+ <dt>kde-needs-ldap</dt>
+ <dd>Bugs related to interaction with a ldap server</dd>
+ <dt>kde-needs-exchange</dt>
+ <dd>Bugs related to interaction with a Exchange server</dd>
+ <dt>kde-needs-home-on-nfs</dt>
+ <dd>Bugs related to having home on a kind of network file system</dd>
+ <dt>kde-fancy-x</dt>
+ <dd>Bugs related to special settings related to X. Including, but not limited to xinerama, transluciency, compiz, beryl and openGL in general</dd>
+</dl>
+
+</body></html>
More information about the pkg-kde-commits
mailing list