When the team has notified me that they are ready to create a release branch I do an svn copy from the trunk to a new branch name. For example, when 0.6 was ready to start it's release checklist I created a Chandler_0.6 branch:
chandler/
branches/
Chandler_0.6/
I name it Chandler_0.6 to make it clear that it's Chandler and that
it's not a release tag. When a release is ready what I then do is
create a 0.6 branch/tag:
chandler/
branches/
0.6/
What I see that needs to change to support Heikki's proposal is that I
would create the 0.6 branch/tag in the tags directory:
chandler/
tags/
0.6/
One thing that should not change is the name of the branch/tag as the
current distribution process folds the branch/tag name directly into
the distribution name.
The biggest reason we haven't moved the current branches and/or tags into some sort of archive directory is that is was pointed out that there may be links to the current names.
--- Bear Build and Release Engineer Open Source Applications Foundation (OSAF) [EMAIL PROTECTED] http://www.osafoundation.org [EMAIL PROTECTED] http://code-bear.com PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
PGP.sig
Description: This is a digitally signed message part
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
