Coordination: updating bug status regularly

[Gustavo Niemeyer]

> I actually think in general the juju team has been pretty good at
> attaching branches to bugs and making it quite clear when they are
> working on a bug. The In Progress status would have been clearer, but
> IMO, when there's a branch linked to a bug, its best to go examine that
> branch before proceeding.

My understanding is that it wasn't assigned until late.

> I don't think announcing on this list is necessary for coordination.. but
> I do think everybody should be more careful to assign bugs to themselves
> before working on them.

It feels quite cheap and useful to send an email to the list for
coordination to save many working hours. Even because it's often the
case that we may have input about how to solve the problem.

> One aside, Gustavo, does lpad automatically assign the bugs it creates
> to the creator?

It assigns, puts in progress, and targets to the current milestone. It
does the same for existing bugs too, with -bug <n>.

That said, this isn't useful unless an empty branch is pushed with
"lbox propose -prep" at the start of the task. If the branch is ready,
then it's too late.

-- 
Gustavo Niemeyer
http://niemeyer.net
http://niemeyer.net/plus
http://niemeyer.net/twitter
http://niemeyer.net/blog

-- I'm not absolutely sure of anything.