CPS 3.5.3 will support Zope 2.10

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

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

Hi there,

we didn't get many responses for migration of CPS to Zope 2.12, that's a
bit disappointing : enough people would be interested, but none of them
has time to devote, apparently.

However, there's a piece of good news with respect to support of less
old Zope versions : CPS-3-base works almost out of the box under Zope
2.10. The only thing that needs real work is CPSDesignerThemes, and that
comes hardly as a surprise:
http://trac.cps-cms-org/ticket/2275

I had already made some attempts to launch the unit tests earlier, but I
got somehow frightened by how low-level in Five they used to fail.
However Gawel <http:www.gawel.org> (kudos for him) reminded me at
pycon.fr that he had made successful experiments of serving a CPS portal
in WSGI, thanks to the repoze layer, which is for Zope >=3D 2.10.

So I gave it a try last week (on Zope 2.10.12), got the UI to work in
CPSSkins mode, and started digging in the tests. Once a double event
subscriber registration and the ZMCL test layer of CPSDefault had been
fixed, there were only 2 failures and 13 errors left, 12 of those
looking like a single one.

Therefore, there's no doubt that CPS 3.5.3 will support Zope 2.10.
Further, we'll very probably be able to keep support for Zope 2.9, which
makes for a (much needed) smooth transition of existing instances.
I am currently struggling with myself to actually wait for the 3.5.2
release to finish this work of adaptation.

Reminders: Zope 2.10 is packaged in the current Debian stable (5.0, aka
lenny), that won't last for long, though. The most important thing is
that it opens the road to standard distutils/distribute/buildout
packaging. Working with these standard packaging tools will certainly
lower the entry barrier in our code.

Moreover, everything seems to be faster, but at this point this is
nothing more than a feeling. We'll run the standard funkload benches
that were pushed by Marc-Aur=E8le recently to get a real clue about this.=


Cheers

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


--------------enig88CDE9D7A813178FBC2FAC4E
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/

iQEcBAEBCAAGBQJM3ohOAAoJEOAffZJiF+Z48IsIAN7WYNRffry0rAB/MEpOAMgG
eintsnsmXT5MZJJO2a0envZ5PgdOV5FC7jadxbJr5mQUMAcC11A4QAnk4ckaZIar
DEh8Y1tQFoBFV4d0NPFhHkS2np/kKxSExWZgzFLgDBaaYU8yHsHzavsS1zNqYvSA
cTbcGSwAB3PE8pE94Nbo8strCYh4cLQrZeKRDicwzJSpmrXJE0gM9DlQDUIUADMp
/69B+/uxQo97PBauaHUxqeAjsiGvC6Xz/m5q78DySCGeQXvBmkIGCSw1wrd/v5uv
TndIpqAHwDmK/yeKN99+ZnjAKbT9QVz42m1/wAJSvGFBH0rvcBoYqiXdAx+47H0=
=kePT
-----END PGP SIGNATURE-----

--------------enig88CDE9D7A813178FBC2FAC4E--

--===============1634833105==
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

--===============1634833105==--