How I Patch Piloted lately and some tricks about merge proposals

[Ian Clatworthy]

Vincent Ladeuil wrote:
> Hi all,
> 
> I've been the patch pilot for this ending week and caught up the
> week before... after we realize we were missing a pilot ;)

I think it was meant to be me but I was MIA bug-fixing Explorer 1.0beta
last week. The queue was pretty quiet the week before: I was watching it
daily then.

> The good news is that no plane crash were reported.
> The bad news is that our queue grew a bit.
> 
> It is now under control again and quite short. Congratulations to
> all parties involved !

+1

> And while I'm on asking favors, doc/developers/HACKING.txt has
> been updated to give some clues about branch names (see Making a
> Merge Proposal). It's lovely to see people willing to give back
> and follow the (old) advice to name their branch 'giveback', but
> more and more people are doing it and while we fully appreciate
> the intent, using a name giving an hint on the submission content
> doesn't hurt. Also, many people agree that, when the branch is
> fixing a bug, this bug number must be part of the branch
> name. The important bit here is *part*, please add a very succinct
> description of the content too, who (except John but he's
> cheating) can remember what a bug is about from the number only ?
> Whether you put the bug number at the beginning or at the end is
> still open :-)

Thanks for bringing this up and improving the docs. My bikeshed has the
bug number at the end fwiw. :-)

Once again, thanks for your great work here. It's *really* pleasing to
see the review queue moving along at the pace it now is.

Ian C.