[Zope-Coders] 2.6 release

[Chris McDonough]

Guilty.  I snuck in browser-ids-in-URLs for sessions and a new
signal handler and caused an error log to be created in the database
at startup time.  I don't believe any of these features are major,
they are all documented in the new version of the Zope Book, and in
an alternate reality they might even be considered bugfixes. ;-)
That said, if these features (or others) really make you
uncomfortable, we should get a ruling from King Brian.

- C


----- Original Message -----
From: "Toby Dickenson" <tdickenson@geminidataloggers.com>
To: "Guido van Rossum" <guido@python.org>
Cc: <zope-coders@zope.org>
Sent: Thursday, August 29, 2002 12:52 PM
Subject: Re: [Zope-Coders] 2.6 release


On Thursday 29 Aug 2002 5:23 pm, Guido van Rossum wrote:
> > There seem to be alot of changes going in to the trunk which
were
> > not part of the 2.6 specification, and which are in my opinion
too
> > major for this stage of the release process.
>
> Can you be specific?

This post from Brian suggested that any new feature not complete as
of June
10th (10 weeks ago) would have to be deferred until Zope 2.7. I am
really
thinking about every new feature introduced since then.

http://lists.zope.org/pipermail/zope-coders/2002-June/001372.html



The recent xmlrpclib.py update to version 1.0.0 caught my attention.
The
specification for 2.6 includes an update to version 0.99. Around
mid-June (at
a bug day, was it?) we discussed 1.0.0, but decided it could wait
for 2.7.

Maybe that original decision was wrong - Im still not sure - but I
am
concerned that it is a sign that stability is becoming less of a
priority,
and the possibility of releasing 2.6 imminently is slipping away.



_______________________________________________
Zope-Coders mailing list
Zope-Coders@zope.org
http://lists.zope.org/mailman/listinfo/zope-coders