Branch Imports

Registered by Robert Collins on 2005-10-28

This specification describes how we will enable the importing of non-Baz upstream branches other than MAIN.

Importing branches other than the mainline of upstream projects requires that we branch in the Bazaar from the relevant upstream branch, at the right place. Doing this can be done by heuristics some of the time, but a more robust approach is to allow users requesting an import to nominate the already imported branch to use. We can then use heuristics such as the upstream VCS's metadata or sourcerer's tree distance logic to determine which revision on that branch to branch from.

Blueprint information

Status:
Complete
Approver:
Robert Collins
Priority:
Medium
Drafter:
None
Direction:
Needs approval
Assignee:
David Allouche
Definition:
Obsolete
Series goal:
None
Implementation:
Deferred
Milestone target:
None
Completed by
Robert Collins on 2006-08-16

Related branches

Sprints

Whiteboard

We have decided only to import TRUNK branches for an upstream product. So we don't need to support branches in the import infrastructure.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.