-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Tres Seaver wrote: | |> Jim Fulton wrote: |> ... |> I've gotten enough negative feedback to "z", that I've added an |> alternative 4 |> to the proposal: |> |> 4. Rename the Zope package to Zope2 and provide a legacy Zope |> package | | -1, for reasons I've stated before. This is Zope 3's problem; we | *can't* inflict the pain on the large set of installed production | servers to favor "cleanliness" for the one only installed by | arrow-backed pioneers. We would be *much* better off with the status | quo ante than with such a "solution". | | Tres.
- -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. As a developer, this change is attractive. However, I can't see it as feasible for the real world.
- -- And the glory of the LORD shall be revealed, and all flesh shall see it together: for the mouth of the LORD hath spoken it. Isaiah 40.5
0xD3BDCA53 http://tjf.us/public.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAhmbnAykmMtO9ylMRAkcRAJwP4FBU5oosHN/3rESobu2ow7XUiwCff0Gv yzgfB6TI6uOmDFA3Z3zKn78= =saog -----END PGP SIGNATURE-----
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce