Hi, I did the conversion of main Firebird modules to SVN.
Dne 14.7.2012 17:19, Mark Rotteveel napsal(a): > Now that Jaybird 2.2 is released we want to migrate the CVS client-java > module to Subversion. Is there any documentation on how this was done > for firebird? Nope. As it was one-way, do-once process, there was no point to document it. However, I've used cvs2svn (see http://pypi.python.org/pypi/cvs2svn) and it wasn't so hard although it took a lot of time. But it took so long because the data volume was huge, so every test run took several hours. I also did thorough routine tests, as there was no margin for error (it was no replace but merge, as SVN was already used for other code) and I had to find optimal compromise between history detail (there was no point to migrate some ALPHA, BETA or even RC tags) and data volume, make changes in structure (CVS is flat while SVN isn't) etc. So it took about a month to prepare it, but final execution was over weekend. As Jaybird is small code base with not so huge history of changes like core engine, it should be much much easier for you. Also the cvs2svn evolved a lot since then. The cvs2svn creates a dump file that could be imported into svn (at least it was the way it works back then) via SourceForge shell service. Just make shure the import ADDs, not REPLACE the old repository :) It's also good to take full svn backup (not chekout) before merge. best regards Pavel Cisar IBPhoenix ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
