indicate when canonical upstream source is not maintained in lp when merge is proposed

[Jelmer Vernooij]

I thought I had reported this already, but now can't find that report anywhere. Apologies if is it a dupe.

There's no way to disable merge requests for projects that don't use them at the moment. This causes people to submit merge requests on Launchpad anyway, and leaves us to deal with them. bzr-gtk uses bundlebuggy for example, bzr-svn merge requests by email sent directly to me.

It would be nice if it was possible to indicate a project or branch doesn't use launchpad merge requests. I imagine this would also be useful for vcs-imports, where upstream doesn't use launchpad.

[Jonathan Lange (jml)]

Another way of describing this bug is that Launchpad doesn't provide a way to channel merge proposals to the project's preferred system.

Certainly, disabling merge proposals would be a good first step. What do you think of disabling merge proposals if the project doesn't officially use Launchpad Code?

[Jelmer Vernooij (jelmer)]

yeah, I think saying it as Launchpad not channeling the merge proposals to the projects preferred system is a better description.

Checking if the project officially uses Launchpad Code would be a start, but there are also plenty of projects that do use Launchpad Code officially but still use some other process for merge proposals (bzr-gtk and bzr-stats for example use bundlebuggy, bzr-svn uses merge requests sent to me personally).

Perhaps launchpad could check the child_submit_to setting in the branch and forward merge proposals to that email address if it's set? That would at least cover the cases for the projects I mentioned earlier.