[Zope-Coders] 2.6 release

[Brian Lloyd]

> 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.

:)

Note that technically, we're not breaking the rules since 
2.6 is (inexcusably, mea culpa) still at alpha 1 and we 
don't feature-freeze until the first beta.

That said, I _am_ concerned about stability and we should 
be doing something to vet these changes (even if just a 
heads-up to the list with some reasonable time for people 
to dissent). I'll try to do everything I can to get a b1 
release made next week, at which point we'll make the 
release branch.

Note that while I'm concerned, I'm not terribly _worried_ 
about 2.6 stability, as the 2.6 / head is the basis for 
a number of current projects here at ZC and is being worked 
out every day.

But the point is taken that we need to do a better job at 
tracking / vetting changes that seem too small to justify 
a proposal and associated overhead. I welcome suggestions 
as to what we can put in place to help with that. In the 
meantime I propose that before people checkin even minor 
featurlets that a note should go to the zope-coders / dev 
lists so that basic sanity checking can happen. Even if 
no one responds, at least then we'll have a hysterical 
record of the reason for the change.


Brian Lloyd        brian@zope.com
V.P. Engineering   540.361.1716              
Zope Corporation   http://www.zope.com