Could it be, that you rather meant the following: /cocoon/ /trunk/ <- current trunk (same as HEAD on CVS) /tags/ <- Tags on specific Milestones and Releases /branches/ <- Branches of the cocoon repository /branches/2.1/ <- Cocoon 2.1 branch /branches/new-kernel/ <- current 2.2 code
Yeah, that's what I want. With the additional "lazy branching" for older minor releases, i.e. create branch 2.1 only if it is needed for security patches for example.
Joerg