-----BEGIN PGP SIGNED MESSAGE-----
Jim Fulton wrote:
> Tres Seaver wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> Jim Fulton wrote:
>>> Chris McDonough wrote:
>>>> On Fri, 2005-06-17 at 10:12 -0400, Jim Fulton wrote:
>>>> We have historically always had the opportunity to introduce features
>>>> that preserve 100% b/c (like filestream iterators) in point releases.
>>>> This has worked pretty well for the last few years.
>>> I wasn't aware of this and I don't think it's a good policy.
>>> Feature releases should be backward compatible. Bug-fix
>>> releases should be for bug fixes.
>> Agreed, in theory. In practice, the usual handwave has been to construe
>> the absence of the feature as a bug (with greater or lesser
>> Perhaps we can be more hard-nosed about a "no new features in third-dot
>> releases" policy *after* we get a timeboxed release process in place? I
>> have some recollection that a hard-nosed application of such a policy in
>> ZODB land contributed to the creation of the "dead-end" 3.3 release
>> line, never incorporated in any released Zope2 / Zope3 version.
> Which is just fine IMO.
Such an outcome might be "acceptable", but could hardly be called
I'll note that a *big* pile of potentially useful ZODB features were
pretty much inaccessible to the Zope2 community from the date of the
first 3.3a1 release, nearly two years ago, until the release of Zope
2.8 last month. This timespan, eerily enough, coincides almost exactly
with the life of the Zope 2.7 release cycle.
I know how and why the loss happened (I helped *make* it happen, I'm
afraid), but I don't want it to happen again. Moving to time-based
releases should help with the problem, but we aren't there yet, and
won't be for a year (a successful delivery in December could be a fluke).
Tres Seaver +1 202-558-7113 [EMAIL PROTECTED]
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -