-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Philipp von Weitershausen wrote: |> Troy Farrell wrote: |> |> -1 on alternative 4. This lurker is with Tres. This is a Z3 |> challenge. I wonder how many part-time Zope 2 admins will be happy |> about making this change and having to retest code they've inherited |> from some contract developer. | | Why would they switch to Zope 2.8 if not for the component architecture? | So, if you just "inherited" some code for maintainance, this will | unlikely break your program. In fact, it won't even break your program | when the rename is effective, since we'll keep a facade Zope package | around.
Philipp, not everyone follows well-planned, ideal upgrade practices. Often, upgrades come when they can be had, and even more frequently when there is a security hole and the fix is only available for the latest version or two. I'm remembering this:
This was the occasion for my upgrade to 2.7, which proved to be a learning experience. Fortunately, I used a test instance for my upgrade :)
Deprecation errors are nice, but usually admins take one of two 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 [EMAIL PROTECTED] list.
This will cause many a shock when the occasion for upgrade to 2.9 comes around. ~ At 2 A.M.
As for moving to CA, I'm trying it right now. I'm working through buddydemo and trying to wrap my head around the verbosity that is Zope 3. My plan is that starting mid-May, all new projects will be on Zope 3 sans the backward compatibility stuffs.
My personal preference is for option 1 or option 3.
Troy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAhnF8AykmMtO9ylMRAh31AJ9EmIAtssh9k/CiNFGGMMQRxK0WSACeIRms 1iq79Ikc982nJvp/X15oETE= =5Kuy -----END PGP SIGNATURE-----
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce