Launchpad itself

How do merges work?

Asked by brisvegas

I might be the stupidest person on this site but I'm completely confused by the process of merging on the Launchpad site.

Does the process of proposal for merge and then approval actually merge a branch in the Launchpad site or do you just do this request and acceptance process online to tell everyone what is going on and do the merge via Bazaar?

I've tried really hard to find good clear documentation for my type of user, the manager who wants to understand what is happening at a somewhat detailed level. If this is clearly documented, please point me to it.

Thanks!

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Celso Providelo (cprov) said : 		#1

Hi,

Have you read https://help.launchpad.net/Code/Review (and the subsequent pages) ?

The merge-proposal infrastructure doesn't actually merge the code for you after it's approved, mainly because it would involve given the launchpad infrastructure permission to commit to your branch. It doesn't mean it's impossible, it's just not implemented right now.

Instead, the merge-proposal framework, allow users to discuss, review and evaluate proposed changes in a quick but flexible way. It can be used with a variety of policies but defers the merge action to whoever has the required permission to do so via `bzr` command-line.

I hope it clarifies you doubts.

Can you help with this problem?

Provide an answer of your own, or ask brisvegas for more information if necessary.

To post a message you must log in.