[PA] Patch pilot: Dear passengers

[vila]

Hi, 

My name is vila and I've been your Patch Pilot this week.

We started our flight at (OMG) ~35 and we are now flying at a more
reasonable 8 (pun intended (especially with a french accent)):

  http://webnumbr.com/bzr-active-reviews [1]

During this flight you may have enjoyed the continuous flow provided by
Jelmer in his triangulation work in the bzr code base aiming at making
the foreign plugins share as much code as possible with bzr itself
(which means a better interoperability including imports).

Related discussions are still going on so now is a good time to check
how it can change your bzr usages.

INADA Naoki started working on i18n/l10n for bzr and since I'm not that
polyglot myself I asked David Planella (Rosetta guru) to join the
discussion (thanks for that David !):

  https://code.launchpad.net/~songofacandy/bzr/i18n/+merge/59890

Discussions are now happening on the mailing list too but you may be
interested by the discussion started in the first proposal.

INADA Naoki also restarted working on bug #523746
(https://code.launchpad.net/~songofacandy/bzr/fix-523746-dev/+merge/20537)
for which I asked windows experts to chime in (I'm not a windows expert
either especially when it comes to the Unicode weirdness there).

While I was marking merge proposals as 'Work In Progress', I was
reminded that sweeping dust under the carpet may not be the main task of
a Patch Pilot (http://webnumbr.com/bzr-wip-reviews)... and indeed it's
not :)

As part of my duties I'd like to remind you that, as passengers, you're
supposed to check your works in progress on a regular basis:

  https://code.launchpad.net/bzr/+merges?field.status=WORK_IN_PROGRESS&field.status-empty-marker=1

Have a look there

  https://code.launchpad.net/~<your_lp_login_here>/+merges?field.status=WORK_IN_PROGRESS&field.status-empty-marker=1

before leaving the plane as these are your belongings and while all
Patch Pilots will check periodically, it's nice to tidy your proposals !

Marking a merge proposal appropriately is still a useful thing for
reviewers (not only Patch Pilots) as it helps focusing on the proposals
that are *waiting* for a review.

Launchpad is quite good to track discussions and intermix the commit
messages when you push additional revisions after reviews. So even if
your proposal is landed across several reviews, it's nice to keep
working on the same branch (and create different merge proposals when
needed) as it makes the shared history clearer.

This also means that one shouldn't be shy about proposing early versions
of his work just to get feedback. 'Work In Progress' conveys this
precise meaning.

But back to the dust/carpet topic, I am now approaching our destination
airport and wanted to remind you that:

   Yes we land !

   http://webnumbr.com/bzr-merged-reviews [1,in the end there should be
   only one... footnote...]

Thanks you for flying with us, I hope you'll enjoy your flight next week
with Andrew,

           Vincent

[1]: Courtesy of... your Patch Pilot this coming week !! <applause>