Initialize shared-repository to maintain several branches
Full explanation of how to create a shared repository in-line with the siesta-maint.
Blueprint information
- Status:
- Complete
- Approver:
- Nick Papior
- Priority:
- Undefined
- Drafter:
- Nick Papior
- Direction:
- Needs approval
- Assignee:
- Alberto Garcia
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
- Informational
- Milestone target:
- None
- Started by
- Completed by
- Nick Papior
Related branches
Related bugs
Sprints
Whiteboard
Any developer wishing to periodically track and/or commit to the siesta code base is encouraged to use the "shared repository" format of bzr.
To conform with the siesta maintainers you should follow these steps to create a shared repository.
In the following we will follow a recipe for creating a new siesta shared repository:
1. Create folder to contain the root shared repository:
mkdir siesta
2. Make bzr aware of the directory as a shared repo:
bzr init-repo --pack-0.92 siesta
3. Go into the siesta folder and branch of the trunk, and possibly any other branch you wish to keep locally:
# create the trunk version and call it "trunk", the first branch will take "forever" to create
bzr branch lp:siesta trunk
# create the 4.0 release series and name it 4.0, this will be much faster to create
bzr branch lp:siesta/4.0 4.0
keep adding branches until you have those you need.
Basically these steps ensures a single repository for maintaining a shared commit log for shared repositories. Please see this webpage for further details on the advantages:
http://
Now your work-flow is much faster as branching of is a shared action.
* This need not be empty, however, we strongly advice you to do so until you fully understand the implications of the actions in bzr.