Thanks Pier!
Pier Fumagalli wrote: > > > - Rename the "xml-cocoon" repository to "cocoon-1" > (you can see the effect of this as now both repositories are > accessible > with the old and new names: they are an alias one of another) > Ok. > - Rename the "xml-cocoon2" repository to "cocoon-2-historic" > (you can see the effect of this as now both repositories are > accessible > with the old and new names: they are an alias one of another) > Ok. > - Create a new repository called "cocoon-2.0" and copy over the > cocoon-2_0_5 > branch of "xml-cocoon2" (clean checkout, and re-import) > (this has been created as a part of this proposal, and it > contains what > it should. All files are down at version 1.1 in this repository) > > - Create a new repository called "cocoon-2.1" and copy over head from the > main "xml-cocoon2" repository (clean checkout, and re-import) > (this has been created as a part of this proposal, and it > contains what > it should. All files are down at version 1.1 in this repository) > So, what will happen, if we release 2.0.5 resp. 2.1? Will we create a new repo for 2.0.6 resp. 2.2? Carsten
