Wiki Tools

  • Find Page
  • Recent Changes
  • Page History
  • Attachments

Differences between revisions 63 and 65 (spanning 2 versions)
Revision 63 as of 2011-10-31 06:17:53
Size: 3757
Editor: mbp
Revision 65 as of 2012-01-17 21:58:59
Size: 3943
Editor: gz
Comment: Add pilots for the next few weeks
Deletions are marked like this. Additions are marked like this.
Line 48: Line 48:
|| 28 Nov w48 || poolie ||
|| 5 Dec w49 || vila ||
|| 12 Dec w50 || jelmer ||
|| 19 dec w51 || gz ||
|| 16 Jan w54 || vila ||
|| 23 Jan w55 || jelmer ||
|| 30 Jan w56 || gz ||

PatchPilot is the Bazaar community scheme to ensure that patches are not ignored or lost in traffic. When people want to improve something in Bazaar, we help them get their patch up to the right standard to land it.

The current pilot is listed in the IRC channel topic of #bzr on irc.freenode.or for easy reference.

The word pilot is in the sense of a maritime pilot: we help patches come through congested waters safely in to harbor.

Tips for pilots:

  • The main thing to watch is the bzr active reviews page in Launchpad

  • When you're piloting, put some concentrated effort into helping people have a good and satisfying experience contributing to Bazaar. Just how you do that is up to you.

  • Send a brief mail before and/or after your stint, to say what you're going to do or what you did, and how it worked out. If you have feedback on the review system or the process, speak up.

  • You're not obliged to deal with all the open patches. We appreciate what you do.
  • You can prioritize whichever you think best achieves the goal of helping people enjoy getting things done in Bazaar. That might be the newest ones, neglected patches, easy patches, or those from new contributors.
  • You can also choose to pick up patches and get them in yourself, by writing tests or fixing things up, or to teach/ask/encourage the original submitter to do these things. Do try to at least explain to the contributor what you're going to do.

  • You can ask (cajole) others to do reviews.

  • You can keep working on patches you're involved with when your stint ends, or you can let the next pilot pick them up. Either way, communicate.
  • If someone's already been asked to do particular changes to get a patch landed, don't move the goalposts without a very good reason.

  • Check that the contributors have executed the Canonical contributor agreement. You can do this automatically using the scan-merge-proposals script from Hydrazine or just by checking their membership of ~contributor-agreement-canonical through the web ui.

  • It's good to get to a specific outcome, so that people know what to do next, and to make this clear in both the text and formal status of the merge proposal. That might be: needs X specific fixes, needs Y tests, needs another review, just needs to be merged.

  • You can also keep an eye on work in progress merges and in progress bugs: these don't currently need review but do represent unfinished work.

  • The recommended way to send approved patches to PQM is using the feed-pqm script from

We started 14 November 2009.



18 Sep w38


26 Sep w39


3 Oct w40


10 Oct w41


17 Oct w42


24 Oct w43


31 Oct w44


7 Nov w45


14 Nov w46


21 Nov w47


28 Nov w48


5 Dec w49


12 Dec w50


19 dec w51


16 Jan w54


23 Jan w55


30 Jan w56


See also: