Thursday, 14 January 2016

Re: "Server" package merges and duplicated effort

According to the
merge should be tracked through a LP bug with an assignee and MoM's
comment column should hold the bug #, but only "If you are not the
previous uploaders". This is the only documentation I found (so far)
on the non technical side of working on merges.

Best regards,

On Thu, Jan 14, 2016 at 10:36 AM, Robie Basak <> wrote:
> On Thu, Jan 14, 2016 at 01:16:20PM +0100, Martin Pitt wrote:
>> Wouldn't it be easier to add a comment to the package on the MoM page
>> to say "joedeveloper is working on that"? That "comment" column is
>> meant for that very purpose :-)
> I think part of the problem is that there are many different locks, and
> different people use different ones.
> * There's the MoM comment column as you say.
> * There's TIL. What does that mean, anyway? The last uploader, the last
> sponsor, do we skip minor and security uploads, do we only use the
> last person who merged? And what if the TIL person is offline or
> unavailable? I think different devs are doing different things here,
> too.
> * Merge bug assignment.
> * Blueprint work item assignment.
> I think this is more of a problem right now as we have many merges in
> flight. More than usual because a pile are being done by people without
> upload rights, so naturally the review process means that merges take
> much longer to complete.
> I also think it matters more where sponsorship is required. I remember
> how frustrating it was to get trumped while waiting for review.
> I'd be happy to pick any one lock method, if it is well-defined and
> there's consensus that that one is the One True Way.
> Robie
> --
> ubuntu-devel mailing list
> Modify settings or unsubscribe at:

Tiago Stürmer Daitx
Software Engineer

ubuntu-devel mailing list
Modify settings or unsubscribe at: