Hi folks,
So, per Benson's message a while ago, I'd like to clean up the WS
subversion repo to reflect our current reality, and then move forward
from there with further site changes, getting rid of commons, finishing
up the orderly shutdown of the "attic'ed" subprojects, etc.
Here is my best-guess plan, and would love your opinions (go for it, you
missed something, NOOOOOOOO!, etc :) ).
--------------
# Context and general questions
We have an "archive" area already where we've placed a bunch of old
stuff. This is where I'm planning to drop the subprojects we've already
voted to "attic", via svn move.
Question - should we in fact move these things, or just leave them in place?
# Disposition
So here's a walk through what we've got, and what I'm guessing to do
with each:
* admin/
Do we need anything in here? Is the planet config actually connected to
anything these days? If not, I'm proposing svn delete for this dir.
* archive/
* axiom/
These don't need touching. See commons below for axiom.
* axis/
This has all been moved to the axis repo, and if I understand correctly
we don't need to keep this around any more. So svn delete it?
* commons/
We need to up-level the active projects in here (commons/axiom -> axiom,
etc) and remove the old ones. So for now, this would mean moving
trunk/modules/[Guththila,java5,util] to the archive/ tree, assuming no
one is relying on java5/ or util/. Axiom, neethi, and tcpmon will get
up-leveled and once that's done we can delete commons/.
* jaxme/
Move to archive/
* kandula/
Moved to Axis, delete
* muse/
Move to archive/
* neethi/
No changes (eventually gets commons/trunk/modules/neethi)
* sandesha/
* savan/
Moved to Axis, delete
* site/
No changes
* woden/
No changes
* wsif/
Move to archive/
* wss4j/
No changes
* xmlrpc/
Move to archive/
* xmlschema/
No changes
--------------
Please let me know if this seems reasonable, or if I'm missing something.
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
