Re: [Oorexx-devel] Switching to Subversion

[Mark H. <m.h...@qu...>]

I'd like to know the reasons why we would want to move to subversion..

a) at all unless we have to
b) in a short period of time without knowing SF's SVN reliability

Cheers, Mark.

PS I have a vested interest in sticking with CVS; I have a work-developed Rexx/DW application that interfaces with CVS that makes working with CVS repositories simple; a better WinCVS than WinCVS, and moving to SVN means having to spend weeks working on an SVN interface :-(

---- Original message ----
>Date: Thu, 23 Feb 2006 11:31:52 -0600
>From: David Ashley <da...@us...>  
>Subject: [Oorexx-devel] Switching to Subversion  
>To: oor...@li...
>
>All -
>
>Rick and I have discussed this and we believe that it will be to the 
>project's advantage to switch to the Subversion (SVN) system from CVS when 
>that become available from SourceForge at the end of this month. But, 
>since we are in the middle of trying to roll out a new release an 
>immediate conversion to Subversion is not practical. So I suggest that we 
>wait until we produce the 3.1 tag in CVS and then convert that CVS release 
>to Subversion. When that is done we can close off access to the CVS 
>repository.
>
>However, we need to come to some consenses about the layout of the SVN 
>tree. For those of you who don't know much about SVN it is very different 
>from CVS in that there is no physical concept of a module, everything sits 
>in a single file tree. You can however design that tree for your own 
>needs. So I have a suggested layout I would like to propose. It woul be 
>similar to the following:
>
>svnrepository
>        oorexx32
>                trunk
>                tags
>                branches
>        oorexx64
>                trunk
>                branches
>                tags
>        oorexx-docs
>                trunk
>                branches
>                tags
>        oorexxtest
>                trunk
>                branches
>                tags
>        oorexxunit
>                trunk
>                branches
>                tags
>        scripts
>                trunk
>                branches
>                tags
>
>In each case the trunk is similar to CVS HEAD and branches and tags are 
>similar to the CVS concepts. The main difference is the addition of the 
>scripts node. I believe we should remove all the sample scripts from both 
>oorexx32 and oorexx64 and place them in a seperate place as they should 
>remain constant for both version of ooRexx.
>
>Ok, let the discussion begin. If you do not have any Subversion 
>experience/knowledge then please aquire some ASAP so you can contribute to 
>this discussion.
>
>Thanks,
>W. David Ashley
>IBM Linux Technology Center
>Linux Installation & Open Object Rexx Team
>IBM Phone: 512-838-0609 T/L 678-0609
>Mobile Phone: 512-289-7506
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by xPML, a groundbreaking scripting language
>that extends applications into web and mobile media. Attend the live webcast
>and join the prime developer group breaking into this new coding territory!
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>_______________________________________________
>Oorexx-devel mailing list
>Oor...@li...
>https://lists.sourceforge.net/lists/listinfo/oorexx-devel
--------------------------------------------------------------
Mark Hessling http://www.rexx.org/
Author of THE, Rexx/SQL, Rexx/cURL, Rexx/DW, Rexx/curses, etc..
Project Manager of ooRexx
Maintainer of Regina
Use Rexx ? Join the Rexx Language Association: http://www.rexxla.org/
Google Earth: 27d43'43.10"S,153d02'20.03"E