Usertagging

Differences between revisions 10 and 11
⇤ ← Revision 10 as of 2011-03-21 11:55:43 →
Size: 4076
Editor: host86-178-84-244
Comment: gender neutral
← Revision 11 as of 2011-03-22 11:06:35 → ⇥
Size: 4091
Editor: host86-180-154-23
Comment: more neutral language about why this is important
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
 * 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.		  * It allows them to be accurately tracked for reporting and statistics collection
 * It will help to highlight Ubuntu contributions to Debian
 * It might help identify blockage in getting patches into Debian (such as an inactive or unresponsive maintainer)
 * It might help to motivate merging of patches by providing a to-do list

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 them to be accurately tracked for reporting and statistics collection
  • It will help to highlight Ubuntu contributions to Debian
  • It might help identify blockage in getting patches into Debian (such as an inactive or unresponsive maintainer)
  • It might help to motivate merging of patches by providing a to-do list

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 their Ubuntu hat (if they have 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.

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

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

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

  • natty: means that the bug was reported during the natty 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 lucid release cycle, should have the following usertags: origin-ubuntu ubuntu-patch lucid

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

Using usertags

  • When submitting a bug, using the 'submittodebian' script: You're done! submittodebian adds tags for you. 

submittodebian

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

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

  • 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 "maverick" 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 maverick

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

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

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

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)