Re: [Zope3-dev] Re: [Zope-dev] Proposal: Move to subversion for source code control of the Zope and ZODB projects

2004-04-12 Thread Jim Fulton
Jamie Heilman wrote:
Jim Fulton wrote:

I propose to move from CVS to subversion for the Zope and ZODB projects;

 http://dev.zope.org/Zope3/MovingSCMToSubversion


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:[EMAIL PROTECTED]   Python Powered!
CTO  (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com   http://www.zope.org
___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Proposal: Move to subversion for source code control of the Zope and ZODB projects

2004-04-11 Thread Jim Fulton
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:[EMAIL PROTECTED]   Python Powered!
CTO  (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com   http://www.zope.org
___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Proposal: Move to subversion for source code control of the Zope and ZODB projects

2004-04-11 Thread Jamie Heilman
Jim Fulton wrote:
 
 I propose to move from CVS to subversion for the Zope and ZODB projects;
 
   http://dev.zope.org/Zope3/MovingSCMToSubversion

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

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )