Usertagging

Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2009-04-27 12:58:09 →
Size: 3648
Editor: 82-69-40-219
Comment: update to karmic
← Revision 5 as of 2009-09-15 19:54:10 → ⇥
Size: 3835
Editor: eth3
Comment: Add reportbug example
Deletions are marked like this. Additions are marked like this.
Line 38: Line 38:
 * '''When submitting a bug, using the 'reportbug' script:'''

{{{
reportbug --bts debian -P 'User: ubuntu-devel@lists.ubuntu.com' -P 'Usertags: origin-ubuntu karmic' -T patch
}}}

Using BTS usertags for bugs submitted by Ubuntu developers

When submitting bugs to Debian, it is recommended to use BTS usertags. This has several advantages:

  • It allows to keep track of them.
  • It will help showing Debian that Ubuntu contributes to Debian.
  • It might help showing Debian that some Debian developers are not being helpful (ignoring patches for a long time).
  • The fact that bugs are visibly tracked could make Debian developers integrate patches faster.

Usertags you should use

All those usertags must be used with the ubuntu-devel@lists.ubuntu.com user. (the user is just used to store the tags, so it's safe to use that address)

  • origin-ubuntu: means that the bug was reported by an Ubuntu developer or contributor, wearing his Ubuntu hat (if he has several hats). This includes bug including or not including patches. This tag should be added to all bugs we talk about in this page.

  • ubuntu-patch: means that the bug includes a patch to fix the issue provided by an Ubuntu developer or contributor.

  • hardy: means that the bug was reported during the hardy release cycle.

  • intrepid: means that the bug was reported during the intrepid release cycle.

  • jaunty: means that the bug was reported during the jaunty release cycle.

  • karmic: means that the bug was reported during the karmic release cycle.

Later (after several release cycles), this will allow to answer questions such as:

  • what are the bugs reported during the hardy release cycle that are still open, now that we are in the intrepid release cycle?
  • how does the number of bugs reported by Ubuntu developers evolves?

Examples:

  • A bug including a patch, submitted during the karmic release cycle, should have the following usertags: origin-ubuntu ubuntu-patch karmic

  • A bug NOT including a patch, submitted during the karmic release cycle, should have the following usertags: origin-ubuntu karmic

Gory details about usertags

  • When submitting a bug by mail, one can add pseudo-headers to add usertags. For example, those pseudo-headers add the usertags "origin-ubuntu" and "karmic" for the user "ubuntu-devel@lists.ubuntu.com": 

Package: lsof
Severity: important
Version: 4.78.dfsg.1-2
User: ubuntu-devel@lists.ubuntu.com
Usertags: origin-ubuntu karmic

  • When submitting a bug, using the 'reportbug' script: 

reportbug --bts debian -P 'User: ubuntu-devel@lists.ubuntu.com' -P 'Usertags: origin-ubuntu karmic' -T patch

  • For an existing bug, using the 'bts' script: 

bts user ubuntu-devel@lists.ubuntu.com . usertag 123456 + origin-ubuntu karmic

user ubuntu-devel@lists.ubuntu.com
usertag 123456 + origin-ubuntu karmic

Notes

  • If you are submitting a bug with a patch, you can tag the bug 'patch' (that's not a usertag, that's a 'normal' tag), using the following pseudo-header: 

Tags: patch
  • If you are submitting bugs by mail, don't forget to report the bug against the version of the package in Debian, not the version of the package in Ubuntu.

CategoryDebian

Debian/Usertagging (last edited 2013-07-09 10:48:13 by racb)