Sounds good to me. ORO's the first to goto SVN then.
Noel (or any other local to Jakarta infra people), before I go ahead and just make a request, is there a particular process you'd like us to adhere to?
I assume it'd be something along:
1 Serve notice to community so they can all be checked in. 2 Send request to Infra, with name of old module, name of new module (usually same) 3 Receive responses from Infra until complete. 4 Community tests the new module. 5 Community updates their website. 6 Community sends Infra a request to kill the cvs module and avail/ line.
So how much of that is complete crap? :)
Hen
On Fri, 24 Sep 2004, Daniel F. Savarese wrote:
In message <[EMAIL PROTECTED]>, "Noel J. Bergman" w rites:Done.
Thanks Noel! I know these things are normally supposed to go through infrastructure, but I thought I could test it out in the test repository without troubling anyone first. Everything looks good and doing the conversion even helped me detect that at some point I'd checked in html files for the Web site that had literal character values instead of character entities like © in them. I can regenerate those and check them in the next time there's a release. At any rate, if Henri wants a guinea pig, he can send infrastructure a formal request to convert jakarta-oro over to SVN. The default cvs2svn values are fine. e.g., cvs2svn -v --dump-only --dumpfile=oro.svn.dump /home/cvs/jakarta-oro/ svn mkdir https://svn.apache.org/repos/asf/jakarta/oro/ svnadmin load --parent-dir jakarta/oro /x1/svn/asf < oro.svn.dump
Why oro instead of ECS? Only because I jumped the gun with Noel's help and tested the svn conversion. ECS can always go next.
daniel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
