Carsten Ziegeler wrote:
We agreed that we move to subversion as soon as possible. Next friday we will (hopefully) release 2.1.5, so we should move right after the release.
Any volunteers for doing this?
Err... what should we actually do?
I mean, let's say that we have decided that the format will be:
/cocoon/ <- this is the repository /2.0/ /trunk/ <- trunk of 2.0 /tags/ <- tags of 2.0 /2.1/ /trunk/ <- trunk of 2.1 /tags/ <- tags of 2.1
IIUC we just need to ask infrastructure to run cvs2svn to the cocoon-2.1 and cocoon-2.2 repos and put them under "cocoon" as 2.1 and 2.2.
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
/cocoon
