CVS->SVN Was: SVN of ECS
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]
Re: SVN of ECS Re: [Jakarta Wiki] Updated: JakartaBoardReport-September2004
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]
Re: SVN of ECS Re: [Jakarta Wiki] Updated: JakartaBoardReport-September2004
I think that Robert is the best person to answer this. He is the main responsibe developer of ECS. ;-) On Tue, 2004-09-21 at 22:56, Henri Yandell wrote: > >> +Robert Burrel Donkin has volunteered to migrate ECS over to SVN as a trial > >> migration. > > > > it went a bit quiet after i made this offer. if there's interest, i'd be > > willing to push this forward again. > > > > Well, do we know who would be the one to accept the offer? > > As far as I know, ECS doesn't really have a champion anymore. I'd vote for Robert here. > > It seems that the community in general would need to answer: > > 1) Should we goto SVN (likely to be a big problem if we say no)? Yes. Up to the projects to decide when they move. E.g. I hope to use the CVS->SVN move for Turbine as a "cleaning" move for the project to reduce the huge number of turbine CVS repositories. > 2) Should inactive projects (ECS, Watchdog, ...) goto SVN? If they find someone that maintains them: yes. > 3) Any reason why ECS should not be the first to go? No. +1 Go ahead. :-) Regards Henning -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH [EMAIL PROTECTED]+49 9131 50 654 0 http://www.intermeta.de/ RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire Linux, Java, perl, Solaris -- Consulting, Training, Development "Fighting for one's political stand is an honorable action, but re- fusing to acknowledge that there might be weaknesses in one's position - in order to identify them so that they can be remedied - is a large enough problem with the Open Source movement that it deserves to be on this list of the top five problems." --Michelle Levesque, "Fundamental Issues with Open Source Software Development" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
