Re: [Zope-dev] Re: Zope 2.9.4

2006-07-16 Thread Andreas Jung



--On 15. Juli 2006 15:55:42 -0400 Tim Peters [EMAIL PROTECTED] wrote:


[Tim]

I used tags for ZODB until I gave in to complaints about that, and
switched to using revision numbers.  The real complaint about using a
tagged external is that when the tag changes, SVN isn't smart enough
to do an incremental update.  Instead, when you update after an
external tag changes:


[Andreas]

What do you mean with when the tag changes?


Not what I said:  I said [when] an /external/ tag changes.  I mean
when you change an external tag _in_ project A _referencing_ the
external tagged project B.  Here A=Zope and B=ZODB, and the external
tags in question are the ones referencing ZODB from within the
svn:externals properties of various Zope directories.


I am still not completely sure about the problem. Yesterday I created a tag 
for for ZODB 3.6.2 as ../ZODB/tags/3.6.2 and I updated the svn:externals

for the ZODB on the Zope 2.9 branch to this new tag. When releasing 2.9.4
2.9.4 will be tagged as Zope/tags/2.9.4so what will be the problem...
both tags should never be touched...am I missing a particular usecase?


Andreas

pgpkq7UXsgJOp.pgp
Description: PGP signature
___
Zope-Dev maillist  -  Zope-Dev@zope.org
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] Re: Zope 2.9.4

2006-07-16 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Andreas Jung wrote:
 
 
 --On 15. Juli 2006 15:55:42 -0400 Tim Peters [EMAIL PROTECTED] wrote:
 
 [Tim]
 I used tags for ZODB until I gave in to complaints about that, and
 switched to using revision numbers.  The real complaint about using a
 tagged external is that when the tag changes, SVN isn't smart enough
 to do an incremental update.  Instead, when you update after an
 external tag changes:

 [Andreas]
 What do you mean with when the tag changes?

 Not what I said:  I said [when] an /external/ tag changes.  I mean
 when you change an external tag _in_ project A _referencing_ the
 external tagged project B.  Here A=Zope and B=ZODB, and the external
 tags in question are the ones referencing ZODB from within the
 svn:externals properties of various Zope directories.
 
 I am still not completely sure about the problem. Yesterday I created a
 tag for for ZODB 3.6.2 as ../ZODB/tags/3.6.2 and I updated the
 svn:externals
 for the ZODB on the Zope 2.9 branch to this new tag. When releasing 2.9.4
 2.9.4 will be tagged as Zope/tags/2.9.4so what will be the problem...
 both tags should never be touched...am I missing a particular usecase?

Tim is talking about the effect on an existing sandbox when the
developer (or somebody else) changes the 'svn:external'.  He alleges (I
have no reason to doubt him, but haven't observed it myself) that
changing from one tag to another (e.g., from $ZSVN/ZODB/tags/3.6.3 to
$ZSVN/ZODB/tags/3.6.4) is more disruptive to those sandboxes than
shifting the revision number, but keeping the branch the same.

I think for *development* purposes that we can afford to leave the
externals pointing at branch+revision;  however, for making releases, I
think we need to manage the external dependencies such that we trigger
at least the internal checkpoint release of externals.

I *really* wish that there SVN supported something like 'svn ln -r 12345
$ZSVN/foobar/branches/3.5 $ZSVN/foobar/tags/3.5.6' (such that the link
that got created was equivalent to branch + revision.


Tres.
- --
===
Tres Seaver  +1 202-558-7113  [EMAIL PROTECTED]
Palladion Software   Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEukSe+gerLs4ltQ4RAtrkAKC9DAN2QAi7kLaroVjv7rq+D/tqRACgszEK
j6WOf3YGAeYo8F4/nNCQHbw=
=lzTZ
-END PGP SIGNATURE-

___
Zope-Dev maillist  -  Zope-Dev@zope.org
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] 2.9.4? reStructuredText support?

2006-07-16 Thread Richard Jones
On Sunday 09 July 2006 22:56, Jim Fulton wrote:
 Whoever integrated reST didn't even read the documentation, much less
 the code.

FWIW.

The ZReST product was originally released by me around 2002 - before those 
directives existed. According to the docutils HISTORY file, the directives 
themselves added in 2003. The *warning* about them was added in 2004.
The configuration to *disable* them appears to have been added in 2005.

What the hell docutils was doing turning this feature on by default...


Richard
___
Zope-Dev maillist  -  Zope-Dev@zope.org
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 )