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

 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.


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

iD8DBQFCsvsB+gerLs4ltQ4RAkJzAKC/9ZzsDNmhJ7zLC8dOQ77FKowouwCgu5RV
iZ9fsxZWKXYVwY5bVZfwA/g=
=3/4a
-----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 )

Reply via email to