Give instructions for creating the first bzr trunk for new projects
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
After creating a new Launchpad project, Launchpad tells you how to get the first batch of code into it:
-------from https:/
Code for this series
You haven't yet told Launchpad where your source code is for $PROJECT trunk series.
* If the code is already in a Bazaar branch registered with Launchpad link the branch to this series.
* If the code is in a Bazaar branch not yet on Launchpad you can either
o Have the branch mirrored from a remote location by registering a mirrored branch
o Push the branch directly to Launchpad. eg. with
bzr push lp:~$YOU/$PROJECT/trunk
* If the code is in git, CVS or Subversion you can request that the branch be imported to Bazaar.
---------end cut----
This basically assumes that your project is already in source control somewhere other than Launchpad! It does not help someone who has just been developing code on their machine without SCM and now wants to put the project on Launchpad to get the benefits of bzr and collaboration.
I suggest adding another option to that list:
* If the code is not in any source control system at all:
o Create a "trunk" folder and copy your source code into it
o Make that trunk folder a bzr branch and then send it to Launchpad as the trunk series of your project:
- bzr init; bzr add; bzr commit -m "Initial import"; bzr push lp:~$YOU/$PROJECT/trunk
affects: | launchpad → launchpad-registry |
Changed in launchpad-registry: | |
importance: | Undecided → Low |
status: | New → Triaged |
tags: | added: projects series |
tags: |
added: docs removed: launchpad-documentation |
Oops. Also add as the last line of that proposed extra option:
- Then link that branch lp:~$YOU/$PROJECT/trunk to this series
(with "link that branch" as a link to the link branch page)
For extra credit, have following that "link that branch" link actually fill in lp:~$YOU/$PROJECT/trunk as the branch to link when the "link a branch" form is displayed. (This will not be required when bug 396523 is fixed.)