Hey all,
Martin's ambition #48552 involves cleaning up the svn. My ambition #80
is to move to a next-generation versionning system so I can
branch/commit/revert on my machine locally.
The current global plan is loosely:
1. Consult and coordinate with all developers (that's YOU)
2. Plan an approximately four day long 'svn down' period for svn
cleanup which involves:
1. Refractions admins making a dump of the svn
2. Martin taking that dump and applying some magic scripts
of his; as he says in his usual non-chalant way "Well, I
already have scripts for cleaning up svn which I did for
another project and that I would like to apply to
geotools"
3. Test loading the result in an svn locally for evaluation
4. Bumping the refractions svn version to something recent
5. Loading the clean dump back into the refractions svn
server.
3. Evaluating various possible improvements to the infrastructure
including looking at possibly:
A. Distributing the svn with a European copy
B. Moving the master repository over to OSGeo
C. Tracking the master repository with a bzr read-only
branch on launchpad (which cannonical offers to do for
free)
D. Using bzr-svn so users who want to can use bzr while
leaving the master system as svn
4. Evaluating a full shift over to a new versionning system
A. Look at Mercurial (Hg) since Sun is moving Java to that
B. Look at Bazaar since I am doing that anyhow
Parts 1 and 2 are the only concrete parts of this plan, are fully
independent of the rest, and would be useful on their own so Martin is
keen to undertake this work.
WE NEED *YOU* TO:
* Let us know of any release schedule which we should work around
so our 'svn down' period does not interfere with your work. Is
anyone releasing in the first half of January?
* Let us know of any objections you may have to this work.
* Look at SPIKE and wipe out any code you may have in there which
is no longer relevant. Note SPIKE will become redundant with the
next generation reversion systems so perhaps we should drop
this.
* Give us any comments, ideas, or worries you have for this
effort.
QUESTIONS:
* Is udig merely on the same server or actually in the same
repository as geotools?
* Is refractions able to host a clean repository using a more
recent version of svn after this work? Would it be possible to
keep the current svn untouched during the move so we could fall
back on the current situation if anything goes wrong with this
work?
Okay, that is all for now. This email is for notification and feedback
so your comments are desired. Please keep the discussion focused though
to avoid this becoming the excuse to complain about anything and
everything.
Thanks,
--adrian
P.S. On the 'next generation' front, after another marathon session (9
hours and ~80% memory use) I finally got a branch made of the repository
in bazaar! The difficulties have been due mostly to network distance and
memory leaks (currently in the svn client not in bazaar). I'm doing this
first to learn how one of these systems works and then to evaluate using
bzr-svn to use bzr locally and the regular svn master for shared
commits.
/soft/BZR/gtcheckouts/working> bzr log --line --forward --limit=20
1: 2004-05-13 Move repository under gt.
2: 2004-05-13 Move repository under gt.
3: 2004-05-13 Added reminder about MAVEN_REPO
4: 2004-05-13 moved all cvsignore files into svn:ignore and removed
them
5: 2004-05-13 The -all functionality has been added so that all modules
are included in eclipse's .classpath
6: 2004-05-13 fixed namespace issues
7: jgarnett 2004-05-14 removed setPath tests
8: jgarnett 2004-05-14 ignore target directory
9: jgarnett 2004-05-14 ignore generated files
10: jgarnett 2004-05-14 Restores xpath expression for range
11: jgarnett 2004-05-14 Restores xpath expression for range
12: jgarnett 2004-05-14 Fixed testcases (was cut&paste mistakes)
13: jgarnett 2004-05-14 fixed test cases
14: jgarnett 2004-05-15 fixed junit errors
15: jgarnett 2004-05-15 ignore target directory
16: jgarnett 2004-05-15 require trailing comma to include shapefile
17: desruisseaux 2004-05-16 Initial port of Julian Elliott patch for
interactivity
18: desruisseaux 2004-05-16 Initial port of Julian Elliott patch for
interactivity
19: jgarnett 2004-05-16 Just becase the service is down does not mean or
validation plug-in should stop the build
20: desruisseaux 2004-05-16 Added new axis names
-------------------------------------------------------------------------
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
