launchpad help|
⇤ ← Revision 1 as of 2008-03-13 22:34:28
Size: 5321
Comment:
|
Size: 5812
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 28: | Line 28: |
| In Launchpad, each series almost behaves like a sub-project within the project as it can have: | In Launchpad, each series behaves almost like a sub-project, having its own: |
| Line 32: | Line 32: |
| * its own translation effort | |
| Line 34: | Line 33: |
| * milestones specific points in the roadmap * releases. |
* translation effort * milestones - specific points in the roadmap * releases * driver - in effect a release manager. |
| Line 42: | Line 43: |
| A project usually has multiple lines of development, particularly if it has previously produced stable releases. In the Bazaar example you can see: | Here you can see some of the different lines of development from the Bazaar project: |
| Line 48: | Line 49: |
| == Naming a series == | == Naming series == |
| Line 50: | Line 51: |
| It's up to the project what each series represents and what the naming convention is. For example, in the GNOME project, the "development trunk" is a series with an odd version number, such as 2.17. When it is ready for release, it is branched with an "even" version number, such as 2.18. Once GNOME make the stable release, they branch it to create 2.19, the new "trunk". | It's up to each project what a series represents and what naming convention they use. For example, in the GNOME project, the "development trunk" is a series with an odd version number, such as 2.17. When it is ready for release, it is branched with an "even" version number, such as 2.18. Once GNOME make the stable release, they branch it to create 2.19, the new "trunk". |
| Line 54: | Line 55: |
| For convention, we encourage projects to call their development focus "trunk" and to use that same branch for development over time. When creating a new stable series: branch from trunk, create the series and link the branch to that series. This ensures that people who create a checkout of "trunk" don't find that it goes stale because it has later become a stable series. | For convention, we encourage you to call your project's development focus "trunk" and to use that same branch for development over time. When creating a new stable series: branch from trunk, create the series and link the branch to that series. This ensures that people who create a checkout of "trunk" don't find that it goes stale because it has later become a stable series. |
| Line 61: | Line 62: |
| == Series and code == | == Series goals == |
| Line 63: | Line 64: |
| If you have code registered in Launchpad against your current development focus, anyone can create their own Bazaar branch of it using just a few keystrokes. | As series tend to represent planned releases, it's useful to target bugs and blueprints to particular series. These are called series goals and must be approved by either the project or series driver. |
| Line 65: | Line 66: |
| There's more about using Launchpad and Bazaar together later in this guide. However, for now fire up your terminal and try: | [https://edge.launchpad.net/beeseek/ BeeSeek] is a project to create an open source peer to peer search engine. BeeSeek's drivers have marked [https://bugs.launchpad.net/beeseek/+bug/182821 bug 182821] as affecting two of their series, https://edge.launchpad.net/beeseek/hive Hive] and [https://launchpad.net/beeseek/honeybee Honeybee]. |
| Line 67: | Line 68: |
| {{{ $ bzr branch lp:pyroom Branched 41 revision(s). }}} |
||<tablestyle="font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">attachment:beseek-bug.png|| ||<style="text-align: center;">'''Series goal for Hive and Honeybee in BeeSeek'''|| |
| Line 72: | Line 71: |
| This will create a local branch on your machine of the Pyroom text editor's current development focus. Replace ```pyroom``` with the Launchpad name of any project that has code registered against a current development focus in Launchpad. | As you can see, this bug has a separate importance, status and assignee in each series. Launchpad excels at tracking how an individual bug affects different communities and contexts; we'll see more of that later. |
| Line 74: | Line 73: |
| If you want to get the code for a different series, simply specify the series name after the project name: | Anyone can nominate a bug or blueprint as affecting a particular series but only the relevant driver can accept it as series goal. |
| Line 76: | Line 75: |
| {{{ $ bzr branch lp:pyroom/0.1 Branched 26 revision(s). }}} |
== Milestones == |
| Line 81: | Line 77: |
| We'll take a look at using series with each of Launchpad's applications later in the guide, including marking bugs and blueprints as series goals. | If series are lines of development, from which releases are made, milestones are specific points on the road to that release, such as: |
| Line 83: | Line 79: |
| = Milestones = | * beta tests * release candidates * minor point releases. Just like series themselves, you can target individual bugs and blueprints to a particular milestone. However, milestones |
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.
ContentsBRTableOfContents |
Overview
Let's look at how you can use Launchpad to plan your project's development and to record releases:
Series: parallel lines of development within your project, working towards a major release.
Series goals: bugs or blueprints that will be fixed in a particular series.
Milestones: points in the development of a series, such as future minor releases or release candidates.
Releases: previous releases within a series.
Launchpad doesn't impose a particular workflow on your project, so how and whether you use these depends on what value you feel they'll bring.
Series
When we think of the way a project organises itself, there are major lines of development from which releases are "cut". Typically these lines of development represent:
Development trunk: this is the current "tip" of development across the core project community, representing the very cutting edge of work on that project. In general, the only releases made from the development trunk are snapshot, milestone or test releases to generate more widespread testing and feedback.
Stable and supported branches: these represent the latest work on the stable versions of the project, which are still supported. If updated stable releases are to be made they will come from these branches.
Obsolete branches: for major release versions that are now out of date and no longer updated. It's likely that work no longer happens on these branches.
We call each of these "major" lines of development a "series" because they represent a series of releases of the same major version.
In Launchpad, each series behaves almost like a sub-project, having its own:
- branches of code
- bugs marked as affecting that series
- bugs and blueprints proposed as goals for the series
- translation effort
- milestones - specific points in the roadmap
- releases
- driver - in effect a release manager.
Let's take a look at the [https://launchpad.net/bzr Bazaar] project as an example.
attachment:bzr-timeline.png |
Series in the Bazaar project |
Here you can see some of the different lines of development from the Bazaar project:
bzr.dev: the current line of active development and source of snapshot test releases for the next stable version.
1.3: the latest stable version recommended to new users.
1.2, 1.1, 1.0: previous lines of development that produced releases.
Naming series
It's up to each project what a series represents and what naming convention they use. For example, in the GNOME project, the "development trunk" is a series with an odd version number, such as 2.17. When it is ready for release, it is branched with an "even" version number, such as 2.18. Once GNOME make the stable release, they branch it to create 2.19, the new "trunk".
Sometimes, projects also call the trunk "MAIN", a term from the days of CVS.
For convention, we encourage you to call your project's development focus "trunk" and to use that same branch for development over time. When creating a new stable series: branch from trunk, create the series and link the branch to that series. This ensures that people who create a checkout of "trunk" don't find that it goes stale because it has later become a stable series.
When you register a series, the description you give it tells other people what your intentions are. If we look at Bazaar's bzr.dev series overview page we can see that it's described as "...the development mainline where new releases are published".
attachment:bzr-sev-series-overviewtimeline.png |
The bzr.dev series overview |
Series goals
As series tend to represent planned releases, it's useful to target bugs and blueprints to particular series. These are called series goals and must be approved by either the project or series driver.
[https://edge.launchpad.net/beeseek/ BeeSeek] is a project to create an open source peer to peer search engine. BeeSeek's drivers have marked [https://bugs.launchpad.net/beeseek/+bug/182821 bug 182821] as affecting two of their series, https://edge.launchpad.net/beeseek/hive Hive] and [https://launchpad.net/beeseek/honeybee Honeybee].
attachment:beseek-bug.png |
Series goal for Hive and Honeybee in BeeSeek |
As you can see, this bug has a separate importance, status and assignee in each series. Launchpad excels at tracking how an individual bug affects different communities and contexts; we'll see more of that later.
Anyone can nominate a bug or blueprint as affecting a particular series but only the relevant driver can accept it as series goal.
Milestones
If series are lines of development, from which releases are made, milestones are specific points on the road to that release, such as:
- beta tests
- release candidates
- minor point releases.
Just like series themselves, you can target individual bugs and blueprints to a particular milestone. However, milestones
