Keep in mind that unlike CVS, it's insanely easy to move stuff around in SVN. We could start with an initial SVN repository that resembles what we have in CVS (something like Stefan's suggestion) then just move everything to where we want it after the migration. That should certainly make the cvs2svn step easier.
-James On Thu, 2005-02-24 at 15:16 +0100, Daniel Florey wrote: > I've no clue how to convert tags and branches to svn, if cvs2svn is capable > of doing so. > I'd propose to achieve a structure close to the commons project as we might > have several subprojects that can be released independently in future. > So we should have a closer look at the commons svn structure when doing the > migration. > > Daniel > > > -----UrsprÃngliche Nachricht----- > > Von: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Im > > Auftrag von Stefan LÃtzkendorf > > Gesendet: Donnerstag, 24. Februar 2005 10:52 > > An: Slide Developers Mailing List > > Betreff: Re: SVN migration > > > > Yes we should have a vote about this. > > > > I like the idea to maintain the current structure in svn in the first > > step. > > But then we should choose the inital structure tha we want to create in > > svn. > > > > Quite ugly would be : > > > > /jakarta > > /slide > > /old-branches (contains branches reflecting the old structure) > > /old-tags (contains tags reflecting the old structure) > > /old-trunk > > > > Any better ideas? > > > > Cheers, Stefan > > > > James Mason wrote: > > > > > I think Stefan volunteered to do the migration, but I probably scared > > > him off with all my nitpicking about the structure :). > > > > > > I don't see a vote thread (and I don't remember one, but that's no > > > guarantee), so calling a vote seems like a good idea. > > > > > > -James > > > > > > On Wed, 2005-02-23 at 13:00 +0100, Daniel Florey wrote: > > > > > >>Hi folks, > > >>Any news regarding the SVN-migration? Did we already decide to go for > > it? > > >>As far as I remember we wanted to > > >>1. Move the existing repository structure to subversion trying to keep > > the > > >>file history (using cvs2svn). > > >>2. Restructure the repository layout so that it look somehow like this: > > >> > > >>/jakarta > > >> /slide > > >> /server > > >> /branches > > >> /tags > > >> /trunk > > >> /src (content of current jararta-slide/src) > > >> /docs (content of current jararta-slide/docs) > > >> /lib (content of current jararta-slide/lib) > > >> (the other directories go to other locations) > > >> > > >> /clientlib > > >> /branches > > >> /tags > > >> /trunk (partial content of current > > >> jararta-slide/webdavclient/clientlib) > > >> files in current jararta-slide/webdavclient/clientlib > > >> /src (content of current jararta-slide/webdavclient/src) > > >> /lib (content of current jararta-slide/webdavclient/lib) > > >> /ant > > >> /branches > > >> /tags > > >> /trunk (content of current jararta-slide/webdavclient/ant) > > >> /commandline > > >> /branches > > >> /tags > > >> /trunk (content of current ararta- > > slide/webdavclient/commandline) > > >> /connector > > >> /branches > > >> /tags > > >> /trunk (content of current jararta-slide/webdavclient/connector) > > >> /src > > >> /example > > >> /conf (content of current jararta- > > slide/webdavclient/etc/conf) > > >> > > >> /wck > > >> /branches > > >> /tags > > >> /trunk (content of current jararta-slide/wck) > > >> /projector > > >> /branches > > >> /tags > > >> /trunk (content of current jararta-slide/projector) > > >> /testsuite > > >> /branches > > >> /tags > > >> /trunk (content of current jararta-slide/testsuite) > > >> /proposals > > >> /branches > > >> /tags > > >> /trunk (content of current jararta-slide/proposals) > > >> /indexing > > >> /jcrri > > >> /taglib > > >> /tamino > > >> /wvcm > > >> > > >>3. Get this working with ant and/or migrate to maven as build tool > > >> > > >>Anyone working on this topic? I could help to get this done if > > appreciated. > > >> > > >>Should we start a vote on this? > > >> > > >>Cheers, > > >>Daniel > > >> > > >> > > >>--------------------------------------------------------------------- > > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > > >>For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > >> > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
