Andreas Jung wrote:
My recommendation:
1 yr deprecation period as it is now
1 yr + X maintenance period for older branches.
+1
Note that this should also extend to the Zope 3 releases. Zope 3.2 is
part of Zope 2.9 and will hence be used for quite some time. Yet,
bugfixes aren't even
Florent Guillaume wrote:
Christian Theune wrote:
Log message for revision 68700:
--- Zope3/branches/3.3/src/zope/app/intid/__init__.py2006-06-17
03:29:43 UTC (rev 68699)
+++ Zope3/branches/3.3/src/zope/app/intid/__init__.py2006-06-17
04:10:29 UTC (rev 68700)
@@ -47,7 +47,10 @@
Hi,
Tim Peters wrote:
[Christian]
Thanks for the clarification, Tim!
You're welcome :-)
Due to the possible future use of 64-bit BTrees, I'm inclined to go for
the 2-character fix for now and possibly remove it once we hit 64-bit
everywhere.
Yupp. If we remember ... ;)
The BTree bug
Hi,
I'm pretty confident that this change does what it is intended to do
(fix 592 and some inconsistencies along the way).
But as I had to figure out some pretty old code and some of the
architecture and dependencies in zope.app.form.browser, I might have
made a mistake, although I supplied
Philipp von Weitershausen wrote:
Andreas Jung wrote:
My recommendation:
1 yr deprecation period as it is now
1 yr + X maintenance period for older branches.
+1
Note that this should also extend to the Zope 3 releases. Zope 3.2 is
part of Zope 2.9 and will hence be used for quite some time.
On Sun, Jun 18, 2006 at 02:29:14PM -0400, Christian Theune wrote:
Philipp von Weitershausen wrote:
Andreas Jung wrote:
My recommendation:
1 yr deprecation period as it is now
1 yr + X maintenance period for older branches.
+1
Note that this should also extend to the Zope 3 releases.
On Sun, Jun 18, 2006 at 08:30:58PM +0200, Lennart Regebro wrote:
On 6/18/06, Paul Winkler [EMAIL PROTECTED] wrote:
+1, I'd like some way to easily know when a release is no longer
maintained. i.e., what's the X in the above formula.
Well, it's 2 versions, so far. I.e, current release and
--On 18. Juni 2006 14:36:06 -0400 Christian Theune [EMAIL PROTECTED] wrote:
However, Zope 2.8 is still available for stable download ... so we
currently have 7 branches to watch out for.
Yes, but in most cases a fix only affects only Zope 2 or Zope 3. So
we are back to 3.
-aj
--
ZOPYX
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux tlotze.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 6224
Blamelist: ctheune,jens,jukart,regebro
BUILD FAILED: failed failed slave lost
sincerely,
-The Buildbot
