[Octopus-devel] tags in CVS: branches and releases mixed

[Heiko Appel]

Hi,

On Tue, Mar 21, 2006 at 11:37:21AM +0100, Axel Thimm wrote:
> ...
> 
> We need some sort of tagging convention to separate releases from
> branches. I suggest something like
> 
> branch-2-0
>  release-2-0
>  release-2-0-1
>  release-2-0-2
> branch-2-1
>  release-2-1rc1
>  release-2-1rc2
>  release-2-1
>  release-2-1-1
> branch-3-0
> 
> e.g. tags are prefixed in such a way that no one will misinterpret
> them during checkouts or commits.
> 
> What do you think?

looks reasonable. I'd go for that ...

 
> I've prepared a CVS checkout (with manual tuning of -r and -D) that is
> "release-2-0" equivalent. Should I commit it to some "release" tag
> convention?

So far only Miguel took care of tagging the cvs. I'd say if nobody
complains within one day, go ahead and introduce the new convention. 
Once you finished, send some cvs command examples (with -r) so that 
all developers know how to access the different branches/releases.

best wishes,

	Heiko


-- 
 Heiko Appel                               | Tel +49 (0)30 838 53038
 Freie Universität Berlin                  | Fax +49 (0)30 838 55258
 Institut für Theoretische Physik 
 Arnimallee 14, D-14195 Berlin, Germany
 PGP-Fingerprint: 802F 864F ED41 63EA 6A14  8E53 ABB6 A33F 20DA DF94

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://www.tddft.org/pipermail/octopus-devel/attachments/20060321/3ddb3da5/attachment.bin