Re: CPS 3.5.3 and plan for Zope > 2.9 migration

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

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

The plan in my previous post below hasn't been met with hostily, so
let's consider it confirmed.

All Zope 2.10 branches have been merged today. All tests of CPS-3-base
currently pass with Zope 2.9 and 2.10.

IMPORTANT : Five update under Zope 2.9

The side effect for CPS under Zope 2.9 is that we don't ship Five 1.3.2
with CPS any more. To update a bundle, you have to remove Five manually
from your Products directory (hgbundler doesn't do that).
This results in a version bump for Five : Zope 2.9.12 has Five 1.3.11,
Zope 2.9.7, the older supported Zope version for CPS has Five 1.3.8.

This Five removal has to be done now for all continuous integration,
development and validation instances. Please report on any problems.

This should *not* be done for production instances running bleeding-edge
CPS until further notice (or the release of CPS 3.5.3).

As an example, CPSSharedCalendar tests are currently broken with Zope
2.9 (as they are with 2.10, btw).
Consider also that subtleties with views lookup and the like are usually
not detected by unit tests.

Cheers


On 06/27/2011 07:55 PM, Georges Racinet wrote:
> Hello all,
>=20
> CPS 3.5.3 will soon be out, now. As promised, it will offer support for=

> both Zope 2.9 and Zope 2.10.
>=20
> Here's a plan for post 3.5.3 development and support of decently recent=

> Zope versions. Inputs welcome.
>=20
> - promote the 3.5.x series to 'stable' status, create the corresponding=

> branches and declare the trunk (aka default) to be 3.6.0-devel.
> - CPS 3.6 will drop support for Zope 2.9, and ideally should require
> 2.12 or 2.13.
> - CPS 3.4 will become officially unsupported by the community.
> - eggification of all CPS products will be the first action in the new
> development trunk.
> - bug fixes and minor evolutions should be done in the 3.5 branch first=
,
> then merged into the trunk if possible. The 3.5 branch should keep on
> supporting Zope 2.9 and 2.10.
>=20
> That was for the actions, now the remarks and reasons why to proceed
> like this:
>=20
> What remains to be done for 3.5.3 is rather light : mostly a weird
> problem with the recursion of IObjectWillBeMoved and similar events
> (detected by CPSCore unit tests) with Zope 2.10 only, plus some more
> work on the 'special' treat.
>=20
> Several customer projects of mine will go live right over on CPS 3.5.3
>=20
> Since last time the question has been raised on this list, I've been
> thinking a bit more about the migration to Zope >=3D 2.12 and made a fe=
w
> experiments. These show that while it's still possible to keep the old
> way of importing products, it's a major pain to launch the tests.
> Therefore, eggification has to come first, and we need at least Zope
> 2.10 to support it, rather than a direct jump to 2.12 or later.
> Once that's been done, I'm all in favor of a direct jump from 2.10 to
> 2.12/13, but in any case this will progress at its own pace, in a third=

> branch derived from the new trunk if need be.
>=20
> Cheers, don't hesitate to comment on this
>=20
>=20
>=20
>=20
> _______________________________________________
> cps-devel mailing list
> http://lists.nuxeo.com/mailman/listinfo/cps-devel


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


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

iQEcBAEBCAAGBQJODzyYAAoJEOAffZJiF+Z4WJMH/jmAhpmu7Uf/WLiqr3g8JGMV
f+AIdcoQGzpdFI/gwteFAJR332bHBexkQHxG3JRcyHE418CtmZzcRNZVL5ItIaVt
ArEfkQHvinrsB5sxkyhbDHeH87xU96NAI5KzOciYSLEU4Lth/vLSk/2qFyomjCkr
dfS+LUNC17hKHNDY8rXmDDYmIDOy30gmAijsOxniXfDIIFeS7af8+GKaAEBcUyU7
CLMtNMFRcgoTusgMbVmhAIuSRxH/vKz+iiTm/bB0n/fA5oJO6WV7ZWacg3TBIrYC
hgIBQLkgpvK8FQrtl7vAPVKE29KqFJ3FWkZJL6gF13W3cS8cIHcXnxKousxwyaw=
=ocn6
-----END PGP SIGNATURE-----

--------------enigB643AED65F8D4E7F72641C40--

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

--===============0904925406==--