This is a system for tracking the status of merge requests made on mailing lists.
| approve | Reviewer wants this submission merged. |
| tweak | Reviewer wants this submission merged with small changes. (No re-review required.) |
| abstain | Reviewer does not intend to vote on this patch. |
| resubmit | Please make changes and resubmit for review. |
| reject | Reviewer doesn't want this kind of change merged. |
| comment | Not really a vote. Reviewer just wants to comment, for now. |
| Waiting | The request has been submitted, but has not had any "approve", "tweak", "resubmit" or "reject" votes. So its fate is undecided. |
| Semi-approved | The request has one "approve" vote. A second approval is required to make it fully approved. |
| Conditionally approved | The request has been approved, subject to some minor changes. The reviewer will have provided the conditions in the comment box. Those changes should be made before merging. |
| Approved | The request has been approved, and should be merged. |
| Merged | This request has been merged. |
| Superseded | A newer request contains all the changes in this request. This version of the change will not be merged, but the newer one may be. |
| Resubmit | This request has received at least one "resubmit" vote. It should be resubmitted with the requested changes. |
| Vetoed | This request has received at least one "reject" vote. It will not be merged. |
| Dupe | This request is a duplicate of another merge request. |
A list of the votes this request has received.
The requests that you have voted on are shown as bold and italic, with a green background. This is only shown when you have logged in.
| approve | Not voted/not-logged-in |
| approve | You voted |
| Auto | Merges and supersedes of this request can be detected automatically. This is because the revision-id associated with the request is known. |
| Manual | Merges and supersedes of this request must be noted manually. |
Send your request to your project's mailing list.
Start your subject line with [MERGE or [PATCH. Follow-up merge requests can start with Re: [MERGE or Re: [PATCH, but only if they include a patch or bundle. (We don't want to treat every message in a merge request thread as a merge request!)
If you want Bundle Buggy to track the bug ID of your patch, include it in the subject line as #1234, BUG 1234 or bugfix 1234 (case insensitive).
The best way is to use the new bzr send command. This conveniently generates a patch against the right revision, and lets you choose whether to include a bundle with your patch. e.g.
$ bzr send http://bazaar-vcs.org/bzr/bzr.dev
You can also use plain patches, but these are more effort to track.
Please send account creation requests to Aaron Bentley. Your comments are always welcome on the mailing list, whether or not you have an account.
Note: you must have a Bundle Buggy account for vote-by-mail to work.
Reply to the merge request, and include a vote string. The vote string should be bb:VOTE, where VOTE is any of the values listed in What do votes mean?. The vote string must appear at the beginning of a line. You must reply to the actual request, not a message later in the thread, because Bundle Buggy doesn't track mail threads.
Bugs are tracked in Launchpad.
Bundle Buggy's bzr branch is here: http://code.aaronbentley.com/BundleBuggy
Bundle Buggy's biggest inspiration was PatchWork, a patch tracker written in Perl.
The vote-by-mail aspect is common to many bug tracking systems, though these systems don't usually use mailing lists per se. I'm most familiar with Launchpad / Malone, Bug Goo (disappeared?), and the Debian Bug Tracker.
