Launchpad bug statuses

[Colin Watson]

On Tue, Oct 02, 2007 at 04:32:24PM -0300, Christian Robottom Reis wrote:
> On Tue, Oct 02, 2007 at 08:08:28PM +0100, Colin Watson wrote:
> > Ubuntu sets Fix Released when the fix has been uploaded, although it
> > isn't necessarily generally available to users yet (because it may still
> > need to build, be mirrored, etc.). I think this is the right workflow
> > (we don't want to have to mess around gardening intermediate states for
> > the sake of the couple of hours it typically takes, or have to concern
> > ourselves with the semantics in the event that the upload fails to build
> > on some subset of architectures), but perhaps the text could be
> > qualified a little bit here.
> 
> You're talking about the the changelog-bug-closing feature, right?

Yes, or the manual workflow we always used before that.

> I wonder if the right workflow isn't setting the bug to Fix Released
> only when the first binary is uploaded (though that would be more
> complex to implement).

The problem with that is that it doesn't take the bug off the
developer's list when the developer is done, but at some
hard-to-determine future point. Plus it has odd effects: what if it only
builds on ia64 but not on any primary architecture? What if the package
is built for everything but only really matters on powerpc? Without a
more fine-grained notion of what fixes exist where (i.e. version
tracking) or a way to select your bug view by architecture, I think it's
hard to do a better job on this than "fixed source has been uploaded and
binaries should be available to end users shortly".

TBH, I think that binaries not being built is something we should handle
out of band by means of a general pass over the distribution to make
sure all binaries are up-to-date before release; this is what we've done
for every previous Ubuntu release, at any rate.

Cheers,

-- 
Colin Watson                                       [cjwatson at ubuntu.com]