Launchpad bug statuses

[Christian Robottom Reis]

On Wed, Oct 03, 2007 at 07:56:59PM +0200, Emilio Pozuelo Monfort wrote:
> > Isn't the correct way to handle this to add the upstream project to launchpad
> > and set the bug so that it also affects upstream?  Then you can be explicit
> > about the bug's status upstream.
> 
> And that says (or at least I understand) that I don't need to add a
> remote bug watch, but register the project in Launchpad, and then open a
> task for it (without being a remote watch). Then *I* would be able to
> change the status. That just adds a *lot* of work to the workflow, and
> thus I disagree with it.

It's work, but I don't see another way of capturing this information. I
mean, this situation is:

    a) there is no upstream bug tracker or bug we could link to
    b) there is work that needs to be done upstream to fix the bug in
       Ubuntu
    c) we want to be able to detect when it's time to repackage in order
       to fix the Ubuntu task

We could offer an easy way to close the "upstream bug". For instance,
we could allow creating a "virtual bugwatch" that would represent an
email we sent to a contact email address for upstream, and we'd use a
special From: address to allow the upstream developer to reply trivially
to indicate the bug is fixed.

(But somehow, ISTM that this developer would be better served just using
Launchpad itself, even if only via the email interface).
-- 
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125