[Zope-dev] Attention: cvs to subversion transition DONE (I hope :)

[Jim Fulton]

The conversion is done.  All "trunk" development should be done in the
subversion repository for Zope (Zope 2), Zope3, ZODB, ZConfig, and zdaemon.
(zLOG is not broken out as a separate project because it's now only used
by Zope.)

For information on using the Zope subversion repository, see:

   http://dev.zope.org/Subversion

and especially:

   http://dev.zope.org/Subversion/ZopeSVNFAQ

I'm gonna wait a few days before removing files from the CVS head,
just to be safe. :)

I will check in some marker files, warning people to work in svn.

Finally, before the conversion, I tagged the cvs head with the
cvs-to-svn-conversion tag. If you have outstanding head work, you should be
able to update to that tag and then use cvs diff to generate patch files to
be applied to subversion checkouts.

Jim

Jim Fulton wrote:
> I'm about to begin the conversion now. Please don't make any more 
> changes to the
> Zope, Zope3, ZODB, ZConfig, zLOG, or zdaemon CVS heads.
> 
> Jim
> 
> Jim Fulton wrote:
> 
>> I plan to do the transition tomorrow, Tuesday may 11.
>>
>> I'll begin at 10am US/Eastern and be done by 5pm US/Eastern.
>>
>> During this time, I ask that no one make checkins to the CVS head for
>> those projects.  The first thing I will do is to tag the head with the
>> tag: 'cvs-to-svn-conversion'.  When I'm done, I will remove all files 
>> from the
>> heads of the preojects in CVS, except README.txt files giving 
>> subversion access
>> instructions.
>>
>> Jim
>>
>>
>> Jim Fulton wrote:
>>
>>> Jim Fulton wrote:
>>>
>>>>
>>>> Sorry for the false start.
>>>>
>>>> I totally missed a flaw in subversion's handling of text-file line 
>>>> endings.
>>>> I suspect that this is fixable, but it's not going to be fixed today.
>>>
>>>
>>>
>>>
>>> I think that this issue has been "resolved".  I have updated my cvs 
>>> to svn
>>> conversion software to set the svn:eol-style property to "native" on 
>>> text
>>> files so that they will get Windows line endings when checked out on 
>>> Windows
>>> and Unix line endings when checked out on Unix-based systems.
>>> I've updated the demonstration repository with the results of this 
>>> conversion.
>>> Note that it's possible that existing checkouts will need to be 
>>> discarded, as I've
>>> totallly rebuilt the repository.
>>>
>>> To browse the respository:
>>>
>>>   http://svn.zope.org/
>>>
>>> To do a read-only checkout:
>>>
>>>   svn co svn://svn.zope.org/repos/main/<project>/trunk
>>>
>>> or, to do a writable checkout:
>>>
>>>   svn co svn+ssh://svn.zope.org/repos/main/<project>/trunk
>>>
>>>
>>> Developers who add new files will need to set the svn:eol-style
>>> property on new text files. There are ways to automate this and we'll
>>> provide some guidence on this at:
>>>
>>>   http://dev.zope.org/Subversion
>>>
>>> BTW, someone has done some work on that Wiki, which was a copy of 
>>> dev.zope.orf/CVS,
>>> to convert the CVS references and instructions to refer to and 
>>> document Subversion
>>> instead. Thanks! I think that there is still a good bit of work to 
>>> do.  Volunteer help
>>> would be much appreciated.
>>>
>>> I'm thinking of trying again to do the cvs to svn conversion of the 
>>> main-line
>>> development branches (cvs heads) on Tusday May 11. This would entail 
>>> moving
>>> ZODB, Zope 2, and Zope 3 head development to subversion (along with 
>>> ZConfig,
>>> zdaemon, and zLOG).
>>>
>>> Any objections?
>>>
>>> Jim
>>>
>>
>>
> 
> 


-- 
Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org