Launchpad itself

Best practices with release branches

Asked by Kay Roepke

Hi!

I've been wondering what best practices people use for release branches:
We just released a version of mysql-proxy and originally had two active branches, the "trunk" leading towards the release and a feature branch which was to become the base for the next version (which we rebased onto the released trunk and then merged into trunk).

Since I figured people would have a hard time to find the exact branch which we released (version 0.7.1), I pushed a branch that I created by branching the code at the corresponding tag. It works, but seems to be a small hack.

Hence my question: How do other people handle this? Has someone found a good workflow to handle this situation?

I've looked at various other Launchpad-hosted project and many seem to have different branches named like 'lp:project/version' which we would like to adopt as well - only with the caveat that I'd like to do as little as possible to make it happen :)

Thanks,
-k

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Gary Poster (gary) said : 		#1

Hello Kay. Thank you for using Launchpad.

I do what you describe, and that's what is described here: https://help.launchpad.net/Projects/SeriesMilestonesReleases . I'm not an expert in this usage, but it seems like a safe bet.

Gary

Can you help with this problem?

Provide an answer of your own, or ask Kay Roepke for more information if necessary.

To post a message you must log in.