[Zope-dev] Re: [Zope3-dev] Re: Proposal: Rename zope package

[Troy Farrell]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Please pardon my slowness to respond.  Zope is (still) not (yet) my full-time
occupation.

Jim Fulton wrote:
| Troy Farrell wrote:
|>
|> Philipp, not everyone follows well-planned, ideal upgrade practices.
|
| There's only so much we can do for people who don't.

Agreed.   I'm mainly playing devil's advocate because we're moving into the
realm where changes have consequences (unlike the legacy-free nature of Z3.)

| I think your main point is people who skip updates.  Perhaps,
| I should have suggested keeping the legacy Zope package longer?

I think you are right.

|> Deprecation errors are nice, but usually admins take one of two
|
| Warning, not errors

Yep, my mistake.

|> approaches to
|> them, neither of which is ideal:
|> 1) Ignore them since everything seems to work alright
|> 2) See the apocalypse horsemen headed their direction - this results in
|> "URGENT!!! HELP ME PLAESE RIGHT NOW" email on the zope at zope.org list.
|>
|> This will cause many a shock when the occasion for upgrade to 2.9
|> comes around.
|> ~ At 2 A.M.
|
| Would you feel better if we kept the legacy support available longer?

I see this in your email to Tres:

- - We would not enable this by default in 2.9,

Assuming that the note on enabling this in 2.9 is fairly easy to spot (README or
ChangeLog or whatever is appropriate) that should be enough.

I'm not trying to rain on anyone's parade or slow the adoption of Zope 3.  I,
along with everyone here want to see this transition go smoothly.  When the
customer only notices the change due to new functionality, ease of use, or
improved performance, then we will know that we have succeeded.

Troy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAh2lPAykmMtO9ylMRAiWcAJ9dDp9QOwfSDcK/Ko+EYbfioSSyTwCdE0ZV
CswY0tSqsUTKdKx1NT6prbo=
=lbVr
-----END PGP SIGNATURE-----