Defining specific problems and handwaving at solutions (was Re: What's Canonical thinking about Bazaar?)

[Neil Martinsen-Burrell]

On 2009-11-23 11:24 , Aaron Bentley wrote:
> Neil Martinsen-Burrell wrote:
>> If I could create a
>> merge proposal from the command line, this would be a slam-dunk,
>> particularly if it worked in tandem with --fixes to link the pushed
>> branch to the given bug.
>
> "bzr send" is one way to create a merge proposal from the commandline,
> submitting the proposal via email.

Is there a Launchpad email address to which I can send this to have it 
registered as a merge proposal in the Launchpad UI?  Because this seems 
to be what is preferred (required?) for contributing to Bazaar now.

> bzr-pipeline trunk now includes "lp-submit", which will create a
> merge-proposal from the commandline, using the LP API to create the
> proposal.  It works whether or not you've been treating the branch as a
> pipe, but for pipelines it will also handle prerequisite branches.
>
> The --fixes integration is already handled as part of pushing Launchpad,
> which is always a component of submitting a merge proposal.  With bzr
> send, this push can be done indirectly, but the effect is the same.

After doing a ton of small doc fixes this weekend and proposing them as 
merges one after the other on Monday, I understand better the --fixes 
integration.  When I make a local commit with --fixes lp:nnnnnn, then it 
just records that bit of information.  When pushed to Launchpad, that 
information then gets turned into a link between the branch and the bug. 
  Bravo!  That's just what I wanted.  (What about pushed branches with 
multiple --fixes?)

As far as lp-submit goes, I installed bzr-pipeline, but the help for 
lp-submit is terse to the point of nonexistence.  After trying it out to 
figure out how it works, I'd be glad to submit a merge proposal with 
some improved documentation.

Is it possible that after some incubation time, lp-submit could be 
included in Bazaar's included Launchpad plugin?

-Neil