cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niclas Hedhman <nic...@hedhman.org>
Subject Re: Cocoon 2.0.5-Dev snapshot, Was: Sitemap-Engine for 2.0.5
Date Tue, 04 Feb 2003 03:14:42 GMT
On Sunday 02 February 2003 23:49, Pier Fumagalli wrote:
> It depends on what you want to do, "branch out" old releases and let their
> branch "die" slowly, or "branch in" (merge) new ones when they become
> mainstream.... (for example, if we think about branch-ins when 2.1 becomes
> "main version" we'll have to merge it back into head)...
>
> Personally, I prefer "branching out" old releases... But anyway when
> subversion will come, there's not going to be this problem anymore :-)

I have been working with both systems independently, and also with both 
systems concurrently (huhh?).

Branch out old releases works well, provided that the branch's modifications 
will be built for the users, so they don't have to understand branching in 
CVS. That is fairly simple to do.

Branching out new stuff works best for "experimental sections", where one or a 
few developers are working together on something that are perhaps going into 
mainstream later.

Niclas

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message