Proposal: Move to subversion for source code control of the Zope and ZODB projects
I propose to move from CVS to subversion for the Zope and ZODB projects; http://dev.zope.org/Zope3/MovingSCMToSubversion Initially, I propose to move just the repository heads. Maintenamce branches (e.g. Zope 2.6 and Zope 2.7) will remain in CVS. Comments are welcome here, and in the Wiki. I propose to make this a topic of discussion at the upcoming Zope commnity IRC chat: http://mail.zope.org/pipermail/zope-announce/2004-April/001409.html Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
Jim Fulton wrote:
I propose to move from CVS to subversion for the Zope and ZODB projects;
http://dev.zope.org/Zope3/MovingSCMToSubversion
Initially, I propose to move just the repository heads. Maintenamce branches (e.g. Zope 2.6 and Zope 2.7) will remain in CVS.
Finally ... :) +1 Christian
Jim Fulton wrote:
I propose to move from CVS to subversion for the Zope and ZODB projects;
Not adding to the repository my voice should not carry much weight, but I absolutely love subversion here on Windows. -- hilsen/regards Max M, Denmark http://www.mxm.dk/ IT's Mad Science
Jim Fulton wrote:
I propose to move from CVS to subversion for the Zope and ZODB projects;
No complaints from me. I do wonder though... one thing I've noticed about ZC's CVS usage in the past is that you folks never export your code for releases. Indeed, the 2.7.0 source release wasn't even checked out with -P so there's a lot of goofy-looking empty directories in the tarball. A common idiom through a great deal of the code is: __version__='$Revision: 1.201 $'[11:-2] Now... thats a cute hack, but its also a silly waste of time. If releases were exported with -kv, it wouldn't be necessary. If you're going to switch to subversion, could I humbly suggest that you actually follow a release process that obviates the need for that kinda stuff? Changing revision control systems is a perfect time to do that kind of thing as everybody is the mode of learning new a process. -- Jamie Heilman http://audible.transient.net/~jamie/ "Paranoia is a disease unto itself, and may I add, the person standing next to you may not be who they appear to be, so take precaution." -Sathington Willoughby
Jamie Heilman wrote:
Jim Fulton wrote:
I propose to move from CVS to subversion for the Zope and ZODB projects;
No complaints from me. I do wonder though... one thing I've noticed about ZC's CVS usage in the past is that you folks never export your code for releases. Indeed, the 2.7.0 source release wasn't even checked out with -P so there's a lot of goofy-looking empty directories in the tarball.
I'm sure that was an oversight. Thanks for pointing it out. Of course, with subversion, we won't have those stupid directories in the first place.
A common idiom through a great deal of the code is: __version__='$Revision: 1.201 $'[11:-2]
Now... thats a cute hack, but its also a silly waste of time.
Not enough to mean anything. BTW, we're moving away from using this idiom, since Python __version__ variables are not widely used and aren't really intended to track individial file revisions AFAICT.
If releases were exported with -kv, it wouldn't be necessary.
That would break Id variables. We do use $Id$ and I want the full ID string so that the ident command will work. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
From: "Jim Fulton" <jim@zope.com>
Initially, I propose to move just the repository heads. Maintenamce branches (e.g. Zope 2.6 and Zope 2.7) will remain in CVS.
What is the rationale behind not moving it all?
--On Montag, 12. April 2004 13:07 Uhr +0200 Lennart Regebro <regebro@nuxeo.com> wrote:
From: "Jim Fulton" <jim@zope.com>
Initially, I propose to move just the repository heads. Maintenamce branches (e.g. Zope 2.6 and Zope 2.7) will remain in CVS.
What is the rationale behind not moving it all?
I won't be forced to migrate all my existing scripts to use SVN at this time. Using SVN for Zope 2.8+ is ok and a good start to learn using SVN. -aj
Lennart Regebro wrote:
From: "Jim Fulton" <jim@zope.com>
Initially, I propose to move just the repository heads. Maintenamce branches (e.g. Zope 2.6 and Zope 2.7) will remain in CVS.
What is the rationale behind not moving it all?
- Reduce risk - Provide a more gradual transition Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
Jim Fulton wrote:
Lennart Regebro wrote:
From: "Jim Fulton" <jim@zope.com>
Initially, I propose to move just the repository heads. Maintenamce branches (e.g. Zope 2.6 and Zope 2.7) will remain in CVS.
What is the rationale behind not moving it all?
- Reduce risk
- Provide a more gradual transition
Dunno if this got covered on IRC, but could you try migrating the whole repository (branches, tags et al) into SVN, but making it clear that if you want ot patch anything prior to HEAD, you need to do so in CVS. Maybe then Kapil's scripts could be used to keep the SVN in synch with the master repository until such time as there are no further 2.7 releases? (I'll put money on their not being another 2.6 release anyway ;-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
Chris Withers wrote:
Jim Fulton wrote:
Lennart Regebro wrote:
From: "Jim Fulton" <jim@zope.com>
Initially, I propose to move just the repository heads. Maintenamce branches (e.g. Zope 2.6 and Zope 2.7) will remain in CVS.
What is the rationale behind not moving it all?
- Reduce risk
- Provide a more gradual transition
Dunno if this got covered on IRC, but could you try migrating the whole repository (branches, tags et al) into SVN, but making it clear that if you want ot patch anything prior to HEAD, you need to do so in CVS.
Maybe then Kapil's scripts could be used to keep the SVN in synch with the master repository until such time as there are no further 2.7 releases?
Sound's reasonable. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
participants (7)
-
Andreas Jung -
Chris Withers -
Christian Heimes -
Jamie Heilman -
Jim Fulton -
Lennart Regebro -
Max M