From: Ype K. <yk...@xs...> - 2005-02-02 17:25:42
|
On Wednesday 02 February 2005 17:03, Alan Kennedy wrote: > [Brian Zimmer] > >>> I've been wanting to move some files around for awhile. > >>> I think this next release has the potential for some > >>> backward in-compatible changes to Java source files so > >>> this might be a good time to re-organize. A lot of the > >>> code is over 4+ year old so I'm not sure how much we'd > >>> be consulting history anyways. > > [Samuele Pedroni] > >> I often consulted history. Without history is very hard > >> to answer questions e.g. like what bugfixes and features > >> have been ported from CPython sre impl to ours and which > >> are still missing. > > [Brian Zimmer] > > Losing history is really the biggest loss as far as I'm > > concerned. In my own projects and at work I have often found > > that a better laid out directory structure outweighs the > > usefulness of history. If you have a tag at the time of > > the restructuring it's always possible to go back and see it. > > > > It's too bad CVS is awful at this. > > Indeed, I think the jython source base is now suffering from the worst > problems of CVS, and I like the idea of a re-organization. > > However, if there was to be a re-organization, I would *greatly* prefer > a migration to subversion, which is a superior versioning system. Among > other things, it can version directories, and can move files around > without losing history, etc, etc, etc. > > http://subversion.tigris.org > > There are tools for migrating CVS to subversion, but I'm not sure how > good they are at carrying over history, etc, and don't have the time to > research it. But the code re-organisation could then be done *after* a > move to subversion, thus preserving history on files as they move around > the hierarchy. The history is kept by the standard conversion from cvs to svn. Once in svn, renames and moves are also in the history. Apart from the versioned renames, the local diff is also very handy. > However, I don't know how practical migrating to subversion is. If we're The migration script cvs2svn.py is written in Python, what more could one wish? It even migrated .cvsignore to the corresponding svn property correctly in my case. Some planning ahead is already going on, and the rest is moving files in svn and fixing file references in the code. Kind regards, Ype Kingma |