Hi all, I'm surprised there isn't bigger discussion about this. The migration is crucial for the future development of GRASS. It seems that CVS->SVN is not bigger problem for the community.
I am not quite sure about OSGeo, the future, etc. People Intevation.de were offering stable support for many year (big thanks!). BTW, is there anyone from Intevation.de who is following this discussion? >From my point of view is important infrastructure for developers, users. In comparison GForge + CVS(or SVN) + Mediawiki Trac is *much much* more better, integrated, it is fun to work with. I am not sure but I understood that the people from Intevation.de don't want to use Trac or something similar. It seems that GForge is not really used by the community. The change is needed anyway... Best regards, Martin 2007/9/18, Hamish <[EMAIL PROTECTED]>: > Markus Neteler wrote: > > Hamish wrote: > > > Very important to me though is that we get a ViewCVS 0.9.3 interface > > > on par with what we have now. There are a number of different > > > flavours of SCM-web interfaces around, but I've not met one as nice > > > and usable as our ViewCVS yet. (mostly I quite like ours and find all > > > others I've tried to be no where close) I depend on it heavily for > > > diffs and exploring the source tree + code history. > > > > That's technically possible, see Martin's Test-SVN: > > http://josef.fsv.cvut.cz/cgi-bin/viewcvs.cgi/?root=grass7svn > > Very nice. Only minor loss is that you can't instantly see the > number of revisions an individual file has had. e.g. > > http://freegis.org/cgi-bin/viewcvs.cgi/grass6/lib/gis/?sortby=rev > > shows that parser.c is the most edited at rev 1.130. > (it should be split into several files) > > But as the versioning is a SVN thing, I don't think we can help that, so > just a comment. > > > H: > > > How to best archive the "grass" 5 repo without losing the change > > > history? If SCM moves away from intevation.de, we must expect that > > > one day they will want to turn the historical CVS server off. > M: > > Sure - but this can always happen everywhere. > > We could focus on GRASS 7 repo now and spend more time later to do > > a full conversion of grass/ (GRASS 5) with all branches which is > > causing some problems right now. > > I wasn't thinking of migrating the old CVSs to a new live SVN repo, just > archiving them somewhere so if someone wants it they can set it up. > > > Hamish > > _______________________________________________ > grass-psc mailing list > [EMAIL PROTECTED] > http://grass.itc.it/mailman/listinfo/grass-psc > -- Martin Landa <[EMAIL PROTECTED]> * http://gama.fsv.cvut.cz/~landa * _______________________________________________ grass-dev mailing list [email protected] http://grass.itc.it/mailman/listinfo/grass-dev
