Relation between Release and Branch

Asked by Ralf Hersel on 2009-01-21

I don't understand the concept of Launchpad completely.
How can I relate a branch with my code to a release? I don't see the relation between downloadable files (which stick to releases) and source code (which stick to branches). I believe there must be a link between these elements in Launchpad which I haven't seen yet.

Question information

English Edit question
Launchpad itself Edit question
No assignee Edit question
Last query:
Last reply:
Edwin Grubbs (edwin-grubbs) said : #1


Branches can be linked to a bug which is targeted to a milestone. Often, milestones and releases have the same version number, and in a few months, all product releases will be connected to milestones, so a release will essentially be a milestone with downloadable files and a release date.


Edwin Grubbs (edwin-grubbs) said : #2


I forgot that you can also link a series to a branch. If you click on a series on your project's overview page, such as "trunk", there will be another link named "Link to branch". Series are a collection of milestones, for example, milestones 1.0.1 and 1.0.2 would be in the series 1.0.


Ralf Hersel (ralf.hersel) said : #3

Hi Edwin
Thank you for your answer.
That means, the only relation between the source code (at branch) and a download (at release) is via a series. There is neither a direct link between a release and a branch nor a link between a release and a milestone. You said that in a future version of Launchpad, product releases can be linked to milestones; do I understand this right? Even if a milestone can be linked to a release, then there will be no link between the milestone and a branch.

To make a long story short: How is a downloadable e.g. tarball linked to its source code?

Edwin Grubbs (edwin-grubbs) said : #4

Hi Ralf,

You are correct that there is no direct link (just through bugs) between a milestone and a branch. Even though there is a definite relationship between a tarball and a specific branch (or version of a branch), most branches are deleted after they are merged into the mainline. Of course, some projects have several series with their own mainline branch, since multiple major versions are in development at the same time. I think I would like to know a little bit more about your use case. Are you interested in keeping a branch around that is no longer being updated for versions 1.0.1, 1.0.2, 1.0.3, 2.0.1, 2.1.1, 2.2.1, etc., or are you just interested in keeping some subset of branches for released versions? The bzr project rarely has double-dot releases, so they end up with a series with just a single release in it.

Instead of keeping multiple branches around, you might want to just use "bzr tag" to label the specific version inside the mainline branch. It might be more useful for Launchpad to create a link between a release and a tag as opposed to a release and a branch.


Can you help with this problem?

Provide an answer of your own, or ask Ralf Hersel for more information if necessary.

To post a message you must log in.