On Jun 15, 2006, at 11:42 AM, yuppie wrote:
Hi Chris!
Chris McDonough wrote:
For what it's worth, maybe there's some middle ground here. Just
because something is deprecated doesn't need it needs to have a
hard date to be removed. Why don't we just have the first use of
zLOG in each m
Whoot! Nice going guys, sorry I couldn't be more helpful.
- Rocky
On Thu, 2006-15-06 at 19:37 -0400, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Issues Resolved
>
> - "1777: ExtensionClass delattr raises KeyError",
>http://www.zope.org/Collectors/Zope/1777
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16 Jun 2006, at 10:28, Andreas Jung wrote:
My recommendation:
1 yr deprecation period as it is now
1 yr + X maintenance period for older branches.
+1
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFEkm+bRAx5nvEhZLIR
--On 16. Juni 2006 09:12:36 +0100 Chris Withers <[EMAIL PROTECTED]>
wrote:
Even numbered releases are "feature add" releases:
2.12.0 - "okay, lets start adding features"
2.12.1 - "whoops, fixed bug x"
2.12.2 - "added feature y"
2.12.3 - "whoops, fixed bug z"
2.12.0 - "added feature z"
2.14.1
Martijn Faassen wrote:
Chris Withers wrote:
[snip]
Personally, I find non-time-based releases a much nicer prospect: you
only need to move to the next major version when it's ready and
because it contains big new features you really want.
Who is going to develop these big features? What's the
Hi Chris!
Chris Withers wrote:
yuppie wrote:
# Support old-style product metadata. Older products may
# define attributes to name their permissions, meta_types,
# constructors, etc.
[followed by the code that interprets the 'methods' attribute]
So 'methods' is BBB code for con
Tres Seaver wrote:
Unit test coverate for custom products is actually quite good. The
problems are nearly always to do with "third party" products, many of
which have been in "useful stable" mode since long before either
deprectaions or ubiquitous unit testing were part of our community's
develo
Chris McDonough wrote:
An example of cruft removal that is worthwhile: the help system code
has stupid side effects (it writes to an invisible catalog in the ZODB
*at startup!*), and people have an alternate way of viewing the help via
the filesystem. Apparently nobody actually looks at the h
yuppie wrote:
# Support old-style product metadata. Older products may
# define attributes to name their permissions, meta_types,
# constructors, etc.
[followed by the code that interprets the 'methods' attribute]
So 'methods' is BBB code for constructors.
That depends on how y
