don't use bug tasks for transitions

[Michael Bienia]

On 2008-05-31 01:14:16 +0200, Stefan Potyra wrote:
> as overheard on #ubuntu-devel today, please don't use one bug with many 
> different tasks for transitions. The problem with this is, that any 
> subscriber of an affected package will get every mail for a change in that 
> bug (in short: [he/she'll get] "zillion mails" [in which he/she has] "no 
> interest in"[1]).

OK, will do so in the future for the remaining perl 5.10 transition (as
this discussion started about bug #230016).

I've done the first rebuild sponsorship requests (for -perl packages in
main) via seperate bugs, but found it cumbersome (when you need several
requests):
- test if a rebuild works (are the build dependencies already
  transitioned?)
- open a bug on LP to get a bug number
- add bug number to debian/changelog
- create debdiff and attach it to the bug
- subscribe u-m-s
Repeat this for every rebuild request (mostly copy the bug title and
description from the previous bug).

I started then using one bug for all my sponsoring request, as I could
add the bug number to the changelog entry while preparing the test-build
of the package. This made the process much lighter:
- add a changelog entry for the rebuild (incl. bug number)
- check if the package actually builds
- if yes, create debdiff
- attach debdiff to the bug and add a task for that package

This bug got out of control when someone added tasks for all affected
packages :(

It's a nice feature that one can add attachments while filing new bugs
but that doesn't help in case of debdiffs where one needs to know the
bug number in advance.

Michael