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
