Call for comments: Zope and CPS versions

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1191221184==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigFF24D1302E783FF38EE611BF"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigFF24D1302E783FF38EE611BF
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

 Hi everybody, and happy new year

Now that CPS 3.5.2 is almost ready with just a few minor issues to fix,
it's time to think of the future versions and the Zope dependencies.

First, I can confirm that Zope 2.10 support is ready, at least for the
"base" distribution. It won't be released as part of the reference
version of CPS 3.5.2, but we'll have a specific tag instead for those
that want to give it a try. The Zope 2.10 branches will be merged right
after the final release, so that CPS 3.5.3 will support both Zope 2.9
and 2.10.
I will probably myself try and deploy on Zope 2.10 for two non-profit
instances I maintain directly.

While CPS 3.5.2 was all about long waiting new features, among them the
fixing of very old-timers such as the painful decorrelation of flexible
documents with their templates, it is my personal opinion that further
releases of the 3.5.x series should be merely bug fixes and internal
refactors with less implications than, e.g, the recent image widget
refactor.

Here are the questions : when will we drop support for Zope 2.9 ? And
what would be the corresponding version number ?

To the first, I'd like to answer "when it's really worth it", and that
should mean eggification and deployment through zc.buildout.

To the second, given the high number of instances around working on Zope
2.9 that would need a much bigger reinstall effort than before, I
propose that dropping Zope 2.9 translates into bumping the version
number to CPS 3.6

It's hard to see that far in the future, but support for Zope >=3D 2.12
should probably be labelled CPS5 if it ever comes (remember that CPS4 is
an old branch dating back to Nuxeo times, that was supposed to be based
on a JCR connector, and got dropped in favor of a pure Java
implementation called Nuxeo 5)

Opinions ?

--=20
Georges Racinet, http://www.racinet.fr
Zope/CPS expertise, assistance & development
GPG: 0x4862FFF7 identi.ca & twitter: gracinet



--------------enigFF24D1302E783FF38EE611BF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQEcBAEBAgAGBQJNIzOPAAoJEOAffZJiF+Z4g5EIAOCp3MzT9IuL7fgm7IIdJPtU
3dYPQmUF6nmzQ6zJE/ETOtNcUVFHLgNUQ44ubSjHKZwuLPZUraRmgpUeUfGQ3DEm
b1JR3NMGJNRKlnaNIaWtL9xfvmU+N5a/Zd7AKJUZ9Ru+Akh+sKLWnbjHnMDMF/o7
9K9MqFz4hdlY+x7AsMorqCv/YsQVQMaWhL8XB5wL6ZDFFSTCikJI8gkm5ertrZDl
ZSF5UzQuTZZ2RLZKpDuLdmQnL4HmfDEKZMQ2LI7aRG918XD+KrjnINSB79NBnQE5
fL7hKvHR8Cj6M3r52UUBkKE6PJ3MRadN+eEoLSOBD0nDMQIgSeSjFysWV2Wc5no=
=fl2J
-----END PGP SIGNATURE-----

--------------enigFF24D1302E783FF38EE611BF--

--===============1191221184==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel

--===============1191221184==--