Allow merging to projects not using bazaar/on launchpad
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
No seriously.
This is a wishlist item, but let me kinda outline how it'd work. Currently I work with many upstreams that use subversion for their version control. There is a bazaar mirror on launchpad, which is great, but there is a ton of features that this doesn't allow me to use. One of those is a merge request.
What I'd like to be able to do is ask for a merge request like the project is on launchpad, and have LP do the rest. By that I mean that it should open up a bug with the branch as a patch in the project's bugtracker. Also, it should query occationally to see if the patch still applies cleanly on the trunk of the project (through the bazaar import) and if it doesn't apply cleanly try and merge via bazaar (which will do better than patch). If it can automatically create a new patch and update the bug.
Simple, right? :)
| Jonathan Lange (jml) wrote | #1 |
| Changed in launchpad-bazaar: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
This is probably about five separate bugs :)
1. Do merge requests against imported branches -- I'm surprised you can't do this already.
2. Have a better workflow for bug/branch links and merge proposals. I'm talking to Martin A about how we can do this better.
3. Generate patches / bundles for branches that are proposed for merge.
4. Get bug/branch links to communicate with external bug trackers by sending patches.
OK, so that's four. But they are all pretty big. Like I say, I'm not sure the first one is an actual bug. 2 & 3 are on our radar, although I can't point you at exact bugs. 4 is a really cool idea but very very wishlist.