Andreas Jung wrote:
For me, the fact that Zope 2.9.3 still emits
deprecation warnings on a fresh install (zLOG...) is a pretty bad sign.
Deprecation warning is only annoying but not a bad sign. Deprecations
are not a functional problem.
That sends a pretty bad message. It's not really
Andreas Jung wrote:
Right. As a rule we must fix any code in the Zope core that would possibly
spit out a deprecation warning caused by a deprecation warning. At least
for zLOG in Zope 2.9 we (possibly only me) were not totally consequent.
Yes, I noticed your name in svn praise ;-)
Chris
Jens Vagelpohl wrote:
Yes, the 6 month cycle is very short. All of a sudden we have a
situation where a whole slew of releases/branches is out there (2.7,
2.8, 2.9, 2.10, trunk)
Indeed, this seems to be purely an artifact of time-based releases. I'm
sure I'm not the only one who routinely
Chris McDonough wrote:
checkins list. Yes, I know. I know. I'm bad. But all of you have
been there before, I'm pretty sure, so I hope you can sympathize.
...and how!
And why the should the core emit a deprecation warning?
Amen.
the goal here? Removing zLOG is (at least by any sane
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 motivation? I'm
not
--On 14. Juni 2006 07:32:42 +0100 Chris Withers [EMAIL PROTECTED]
wrote:
Florent Guillaume wrote:
Yes but the deprecation has been there for a while, and the third party
product developers have been ignoring the warning. Their loss.
And this is only for Zope 2.10 which I doubt these third
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14 Jun 2006, at 09:44, Andreas Jung wrote:
--On 14. Juni 2006 07:32:42 +0100 Chris Withers
[EMAIL PROTECTED] wrote:
I know the good reasoning behind the time-based releases, but have
they
really worked out?
Yes and No.
Yes: It's a must
--On 14. Juni 2006 10:28:08 +0200 Jens Vagelpohl [EMAIL PROTECTED] wrote:
For me, the fact that Zope 2.9.3 still emits
deprecation warnings on a fresh install (zLOG...) is a pretty bad
sign.
I think this is a dead horse now. Some things were deprecated without
actually converting all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Warning: This is gonna be ranty and will almost certainly contain
foul language. ;-)
I've never actually seen a deprecation warning emitted for zLOG. And
I'm about as in the loop as anybody could expect someone to be, but
I've not actually
On 6/14/06, Chris McDonough [EMAIL PROTECTED] wrote:
The time-based release cycle just amplifies this across many branches
and point releases, so nobody really knows which products work with
what branch/release and under what configuration some feature is
supposed to emit a deprecation warning
On Wed, 2006-06-14 at 13:34 +0200, Lennart Regebro wrote:
On 6/14/06, Chris McDonough [EMAIL PROTECTED] wrote:
Well, ignoring the confusion about zLOG, updating things for a new
version of Zope with deprecation warnings is not much work. Honestly.
You update to the new version, look at the
Chris Withers wrote at 2006-6-14 07:32 +0100:
...
Would be interested to know what other people think...
I like time based releases but I hate deprecations
for cosmetic annoyances (term stolen from Andreas).
I have the feeling that most deprecations so far
have been for cosmetics only.
--
12 matches
Mail list logo
