[Cosmo-dev] Cosmo 0.7.1 release plan

[Mike]

On Sep 4, 2007, at 7:55 PM, Ted Leung wrote:

> - We've only seen one proposal for how to manage branchng, so we're 
> going to do that one, which is to base the 0.7.x branches off of 0.7.  
>  We will merge the changes from 0.7.1 into the trunk when 0.7.1 
> releases, but we will also merge them into 0.7.2 as soon as QA begins 
> so that 0.7.2 development can proceed.   It is going to be important 
> to keep the .7.x branches and the trunk in buildable/releasable 
> states.

I will be able to branch 0.7.1 on demand (well, given an hour's notice)

The plan looks doable - with the caveat that we will all be tweaking as 
we go along.

My thoughts are that as 0.7.x fixes are applied I should also be seeing 
the patches being applied to trunk and that as soon as 0.7.x is signed 
off by QA I will need to create a 0.7.x+1 branch and close 0.7.x

When each branch is created is really up to the dev team.

---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bear at osafoundation.org
http://www.osafoundation.org

bear at code-bear.com
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/cosmo-dev/attachments/20070904/d16be8f6/PGP.pgp