launchpad-dev team mailing list archive

[John Arbash Meinel <john@xxxxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/11/2012 1:48 PM, Graham Binns wrote:
> On 11 September 2012 10:14, Robert Collins
> <robertc@xxxxxxxxxxxxxxxxx> wrote:
>> We garden them as a group, and at the moment we're failing to
>> release things:
>> 
>> https://bugs.launchpad.net/launchpad-project/?field.status%3Alist=FIXCOMMITTED
>>
>> 
shows 48 bugs in 10 different projects, which is perhaps a bit
>> excessive.
>> 
>> I'm wondering how we can handle this better?
> 
> My first thought is that gardening these - or at least prodding
> the owners of the patches - should be a maintenance
> responsibility.
> 
> That said, an automated weekly or monthly nag might be a place to 
> start, something that sends an email to the branch's owner (or bug 
> assignee if they haven't linked a branch) and kicks them about it.
> 
> In the case of bugs where no-one's assigned themselves or linked a 
> branch the script could email the dev list. And then we could hunt 
> down the person who marked the bug fix committed and hit them with 
> sticks for not doing any of the other useful things.
> 

I will say that people have different levels of competency (and care)
to drive a fix all the way through to a full release. So if you make
the barrier "To do any change, you must drive it through to a full
release", could make the barrier for drive-by fixes a bit too high.

I suppose this depends mostly on things that are sourcecode level
changes, because if it is an egg, you at least need to cut a tarball,
right?

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBPC60ACgkQJdeBCYSNAAP4CQCeLoDLUjKIdsDxJzjmdIaKVPJ2
3gkAnjiHlayZKHHcGBAaOdc5vh7gqksL
=wznr
-----END PGP SIGNATURE-----