cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <joerg.heini...@gmx.de>
Subject Re: Moving to subversion - volunteers?
Date Sun, 09 May 2004 08:43:01 GMT
On 09.05.2004 09:35, Upayavira wrote:

> Personally, I would leave 2.0 as is, and then:
> /cocoon/
>  /trunk/ <- current trunk
>  /tags/new-kernel/ <- current 2.2 code
> 
> I would do it this way as, if we are to follow our new versioning 
> scheme, we cannot identify the new kernel with the version 2.2, so we 
> shouldn't use version numbers in our repository names. We should use 
> 'feature names' in our branches/tags. E.g. Forrest has its 'copyless' 
> branch. So we should have a 'new kernel' branch.
> 
> Regards, Upayavira

+1
- leave Cocoon 1.x and 2.0 where it is (or is CVS switched off sometimes 
completely?)
- our development (current cocoon-2.1) takes place on HEAD (no hint on a 
version)
- sandbox as branch (with whatever name, Upayvira's proposal sounds 
good, current cocoon-2.2)

Joerg

Mime
View raw message