launchpad help|
Size: 4781
Comment: work in progress
|
← Revision 14 as of 2023-05-30 14:10:13 ⇥
Size: 3818
Comment: update broken bazaar links and add a note about what is breezy
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| '''DRAFT: this page is a work in progress. Please [[Feedback|seek further help]] or check the [[TitleIndex|wiki index]] for a complete page on this topic.''' | ~-[[FrontPage|Launchpad Help]] > Code -~ |
| Line 5: | Line 5: |
| == Notes == Please note while the name Bazaar is still used, especially in the context of branches and the technology in general, the product Bazaar is no longer maintained and was replaced by [[https://www.breezy-vcs.org|Breezy]]. |
|
| Line 7: | Line 12: |
| Using Launchpad, you can publish Bazaar branches of your code and, optionally, associate them with projects. You can also mirror or watch Bazaar branches published elsewhere on the internet and import Subversion and CVS repositories into Bazaar branches. | Using Launchpad, you can publish [[https://www.breezy-vcs.org|Bazaar]] branches or [[Code/Git|Git]] repositories of your code and, optionally, associate them with projects. You can also mirror Bazaar branches that are hosted elsewhere on the internet and even import git, Subversion and CVS repositories into Bazaar branches. |
| Line 9: | Line 14: |
| This means that it's supremely easy to find all the code associated with a project - even casual contributions - | Thousands of people have done that already, meaning that Launchpad has a huge directory of branches of code. You could think of it as a [[http://news.launchpad.net/general/the-great-source-code-supermarket|code supermarket]] because it's so easy to browse and get hold of the code you want. |
| Line 11: | Line 16: |
| You can use Launchpad, with the [[https://bazaar-vcs.org|Bazaar version control system]], to host branches of code and also to find and use branches of other people's code. | Over the next few pages, we'll look at: |
| Line 13: | Line 18: |
| * downloading and working with code that's hosted on Launchpad * hosting your code on Launchpad * working with a team on the same branch of code * proposing code merges and conducting code reviews * importing code from git, CVS and Subversion repositories |
|
| Line 14: | Line 24: |
| = New to Bazaar or distributed version control? = | |
| Line 15: | Line 26: |
| Launchpad works with the [[https://bazaar-vcs.org|Bazaar version control system]] to provide a directory of and hosting service for free software code. | If you're already familiar with Subversion or CVS, it's worth noting that Bazaar is a [[http://betterexplained.com/articles/intro-to-distributed-version-control-illustrated/|distributed version control system]]. |
| Line 17: | Line 28: |
| As an individual, you can use Launchpad and Bazaar to: | So, with Bazaar, your workflow no longer looks like this: |
| Line 19: | Line 30: |
| * publish, mirror and watch Bazaar branches * associate your code branches with projects * propose branch merges and take part in code review * import Subversion and CVS repositories into a Bazaar branch hosted on Launchpad * download your own version, with full revision control, of any branch of code that's tracked in Launchpad. If you run a project, and optionally associate them with a project * mirror or watch Bazaar branches published elsewhere on the internet * download your own version, with full revision control, of any branch of code that's tracked in Launchpad * import Subversion and CVS repositories into a Bazaar branch hosted on Launchpad. |
1. jump through hoops to get read/write permission for a central code repository 1. check code out of that central repository 1. hack, hack, hack 1. commit code back to the central repository |
| Line 34: | Line 35: |
| Instead, Bazaar lets anyone create their own branch—with full version control—of any other Bazaar branch. That gives everyone much more freedom and tears down the barriers to new and drive-by contributors. When you—as the owner of the main-line branch—want to use something that appears in another branch of your project, Bazaar makes it supremely easy to merge their work into the main-line. | |
| Line 35: | Line 37: |
| Launchpad is both a directory of free software code and a code hosting service. Using the [[https://bazaar-vcs.org|Bazaar version control system]] you can create your own branch of hundreds of free software projects and also | Also see: |
| Line 37: | Line 39: |
| Using Launchpad, you can publish branches of your code and associate them with a project. | * ''[[https://www.breezy-vcs.org/doc/en/mini-tutorial/index.html|Bazaar in five minutes]]'' to learn the basics of Bazaar and set it up on your local machine * and Ian Clatworthy's excellent ''[[http://ianclatworthy.files.wordpress.com/2007/10/dvcs-why-and-how3.pdf|Distributed version control systems - why and how]]'' (PDF). |
| Line 39: | Line 42: |
| Launchpad's code hosting works closely with the [[https://bazaar-vcs.org|Bazaar version control system]] to | You may also find it useful to read the Bazaar project's [[https://www.breezy-vcs.org/doc/en/tutorials/using_breezy_with_launchpad.html|guide to using Breezy together with Launchpad]]. |
| Line 41: | Line 44: |
| With Launchpad, you can find source code for free software projects and also register your own branches of code to be tracked in Launchpad. Launchpad's code hosting | = Where Launchpad comes in = |
| Line 43: | Line 46: |
| Launchpad's code directory - or [[http://news.launchpad.net/general/the-great-source-code-supermarket|supermarket]] - | If you're new to distributed version control, this way of working may seem a little chaotic. Launchpad helps tie everything together by: |
| Line 45: | Line 48: |
| * providing one place to find and download all code associated with a project, whether that code's in official lines of development or branches owned by anyone else * making it easy to distinguish official project lines of development from unofficial branches * giving you free hosting for your code * linking branches of code to the [[Bugs|bug reports]] and [[Blueprint|blueprints]] that they address * offering public code review for proposed branch merges. |
|
| Line 46: | Line 54: |
| Using Launchpad's code directory, you can find and host source code using the | = Next step = |
| Line 48: | Line 56: |
| Using Launchpad, you can host code | Let's start by [[Code/FindingAndDownloading|finding and downloading]] code using Launchpad and Bazaar. |
| Line 50: | Line 58: |
| Launchpad has a code directory, or [[http://news.launchpad.net/general/the-great-source-code-supermarket|supermarket]]. Use the first two paragraphs to summarise all the important points about this article. Tell the reader if this is the information they need as soon as possible. = Instructional text = Where appropriate, use step by step instructions: '''Step 1:''' Give concise and unambiguous instructions. '''Step 2:''' Try not to state the obvious, unless you're writing for a novice user. {i} '''Note:''' Highlight important information with a note. '''Step 3:''' Use a well cropped screen shot if it will help orient the reader. Don't let the screen shot replace instructional text: not everyone can see your screen shot. Don't worry about borders or annotation for small, cropped screen shots such as this. {{attachment:screen-shot.png}} {i} '''Warning:''' If you're about to tell the reader to delete or otherwise change something that would be hard to restore, warn them. == Full screen shots == ||<tablestyle="float:right; font-size: 0.8em; width:30%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">{{attachment:proj-announce.png}}|| ||<style="text-align: center;">'''Describe the screen shot here'''|| Some screen shots will be better placed to the right of your text. As they're not placed directly below the text that they support, use a border and short description. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aliquam sagittis. Aliquam eros dui, scelerisque id, consequat in, accumsan vitae, pede. Suspendisse neque ligula, scelerisque ac, mattis ut, aliquam quis, odio. Proin nunc nisi, fringilla ac, congue ac, luctus eu, lacus. Maecenas ac purus. Cras felis metus, ultricies non, euismod ac, accumsan eleifend, leo. Quisque imperdiet tempus tellus. Ut euismod, diam nec adipiscing interdum, tortor orci fringilla nisi, vel blandit erat magna at nisi. Fusce hendrerit odio non metus. Mauris nisl massa, dapibus id, feugiat quis, blandit a, quam. Integer tincidunt feugiat nunc. Curabitur iaculis egestas elit. Nam imperdiet suscipit odio. |
||<tablestyle="width: 100%;"> ~-[[Translations/YourProject|< Translations for project owners]] -~ ||<style="text-align: right;"> ~- [[Code/FindingAndDownloading|Finding and downloading code >]] -~ || |
Launchpad Help > Code
Notes
Please note while the name Bazaar is still used, especially in the context of branches and the technology in general, the product Bazaar is no longer maintained and was replaced by Breezy.
Overview
Using Launchpad, you can publish Bazaar branches or Git repositories of your code and, optionally, associate them with projects. You can also mirror Bazaar branches that are hosted elsewhere on the internet and even import git, Subversion and CVS repositories into Bazaar branches.
Thousands of people have done that already, meaning that Launchpad has a huge directory of branches of code. You could think of it as a code supermarket because it's so easy to browse and get hold of the code you want.
Over the next few pages, we'll look at:
- downloading and working with code that's hosted on Launchpad
- hosting your code on Launchpad
- working with a team on the same branch of code
- proposing code merges and conducting code reviews
- importing code from git, CVS and Subversion repositories
New to Bazaar or distributed version control?
If you're already familiar with Subversion or CVS, it's worth noting that Bazaar is a distributed version control system.
So, with Bazaar, your workflow no longer looks like this:
- jump through hoops to get read/write permission for a central code repository
- check code out of that central repository
- hack, hack, hack
- commit code back to the central repository
Instead, Bazaar lets anyone create their own branch—with full version control—of any other Bazaar branch. That gives everyone much more freedom and tears down the barriers to new and drive-by contributors. When you—as the owner of the main-line branch—want to use something that appears in another branch of your project, Bazaar makes it supremely easy to merge their work into the main-line.
Also see:
Bazaar in five minutes to learn the basics of Bazaar and set it up on your local machine
and Ian Clatworthy's excellent Distributed version control systems - why and how (PDF).
You may also find it useful to read the Bazaar project's guide to using Breezy together with Launchpad.
Where Launchpad comes in
If you're new to distributed version control, this way of working may seem a little chaotic. Launchpad helps tie everything together by:
- providing one place to find and download all code associated with a project, whether that code's in official lines of development or branches owned by anyone else
- making it easy to distinguish official project lines of development from unofficial branches
- giving you free hosting for your code
linking branches of code to the bug reports and blueprints that they address
- offering public code review for proposed branch merges.
Next step
Let's start by finding and downloading code using Launchpad and Bazaar.
