Send merge proposals as patches to upstream

[Jonathan Lange]

Merge proposals are great, but we're starting to notice that lots of projects that don't actually use Launchpad for code review are getting people submitting patches as merge proposals. These contributions languish on the Launchpad tracker with upstream never noticing them.

Wouldn't it be great if Launchpad could be told how to submit patches upstream, and for those patches to be sent upstream automatically?

[Jonathan Lange (jml)]

I think this is very cool, but it needs a lot of design first.

[Tim Penhey (thumper)]

Hmm... if the person who registered the trunk branch set the default review team to a team that is the upstream mailing list... perhaps this almost fits.

[Jonathan Lange (jml)]

On Fri, May 1, 2009 at 2:15 PM, Tim Penhey <email address hidden> wrote:
> Hmm... if the person who registered the trunk branch set the default
> review team to a team that is the upstream mailing list... perhaps this
> almost fits.
>

Almost. This isn't quite good enough to integrate with the way the
Bazaar team handle patches.

It certainly isn't good enough to work with a project that takes
patches as attachments to roundup / trac bugs, nor for projects that
use git/svn/hg branches for bugfixes.

jml