Jody Garnett a écrit :
> We should get this over with as soon as possible (I was hoping we could 
> do it during the break for the holidays). My understanding is it will 
> take a couple days of svn being offline?

It may take a couple of days, but I'm not sure that SVN would need to be 
offline.

* I can experiment on a SVN dump and put all my "svndumpfilter" commands in a
  script. When the result seems good enough, I can ask for a new dump, call for
  a "everyone out of the pool" just at that time, launch the script, let it work
  all night and take it over next moorning.

* If some commits happen during the "everyone out of the pool" time, it still
  possible to execute "svn diff" on the old SVN and "patch" on the new SVN.
  However it would handle only changes, probably not file addition or removal
  (it would probably be safer to respect the "everyone out of the pool" call).


> Cleaning up (and moving?) svn seems like a great goal. I have really 
> scared of moving to a new version control system. Reasoning - tools 
> support is needed for us to get more new developers, now that we have 
> some tool support for svn we are starting to get a lot more exciting 
> unsupport modules created, tool support for a next-generation versioning 
> system is likely to lag.

I have hesitation to move to Mercurial too. It is really a different way to
think about code repository, but I understand that it is the reason that may
make it appealing. However at this time I'm rather happy with SubVersion - it
work well for me and I suspect (but have not verified) that it may be possible
to create a Mercurial mirror synchronized on a SVN repository. So I would said
"really worth experimenting as a mirror, but no rush".


> I am still waiting to hear back about what a good target server is. The 
> choices were OSGeo and CodeHaus. I was worried the geotools community would
> be stuck keeping svn up and running - but it looks like OSGeo is already 
> got that going (and the username / password is already intergrated with 
> their wiki etc...).

My personal preference would be OSGEO. If we had a volunter for moving the WIKI
to OSGEO, I would probably be pleased since I'm a little bit annoyed by all the
ads on CodeHaus and I'm pleased with the "wikipedia-like" look of OSGEO wiki.


> No objections; I think a break out IRC on the topic would be a plus 
> since it would be good to move on this stuff earlier rather than later.

We could raise this topic at IRC meeting next Monday. I really hope to finish
this endless IFREMER work by that time...

        Martin

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to