CPS 3.5.1-rc2 & new CPS trac

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

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

Hello everyone,

The second release candidate for CPS-3.5.1 has just been tagged and is
available on http://download.cps-cms.org.

We are inviting everybody to install and test it, reporting issues in
the relocated and upgraded bug tracker at http://trac.cps-cms.org
(registration needed)

The previous release candidate had been announced on the cps-devel list
only. Quoting myself:

> CPS 3.5.1 is a very special release, since it sports the full
> unicodification of the framework. This means changes all over the code,=
 upgrade steps, etc.

Since rc1, the CPS site at http://aful.org has taken the plunge. In the
process, we fixed a few bugs, mostly related to upgrades.

Distance to 3.5.1 release
-------------------------
Here's the list of open tickets: http://trac.cps-cms.org/report/15
And those seen on 3.5.1rc1:
http://trac.cps-cms.org/query?version=3D3.5.1rc1
For rc2:
http://trac.cps-cms.org/query?version=3D3.5.1rc2

Situation of upgrade process
----------------------------
Upgrades aren't really the main focus yet, though we need them already
for the applications we maintain ourselves. Of course we'll try and
provide as much help as possible.

We will probably have to work on upgrades in the whole CPS 3.5 series

  - from CPS 3.5.0 : if you have a set of profiles meant for regular
upgrades, no custom code and upgraded custom configuration (not that
much), it should be a matter of documentation only and almost automatic,
thanks to a decicated CPS job. Everything that does not work straight in
these conditions counts as a bug.
  - from CPS 3.4.x : same plus upgrade to CPSDesignerThemes (documented,
but still a few traps)
  - from CPS < 3.4 : you would have to start creating a set of profiles
reproducing your configuration in an easily upgradable way, ie: make a
really good upgrade to CPS 3.4, and then go the way up.


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


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

iQEcBAEBAgAGBQJMVySvAAoJEOAffZJiF+Z4Ja0H/RrX9TrnoSZnYcjtNtKvpdka
4tJDIlNRQJtlsKkPBkGzV7sv3j17EPulD+hAJKrihmBE4p9m8s+nE0o4jZKKiy3n
swHgZeyBTRFm6d71HVfmz/06QwZ+3E/U9Jt8FcHY3YlpTTodgjM3MwUmPOv0IB3d
X9UZKFXs3O0DTRIhh+L0XzUBWaPbx9InCt0wdQ0OJYSYLDdVV3HvycSX5RtQ6oGS
HAf4nchDNqQrQtDxMGDey+mIvvOE8JtVvfmUr0TUD0yDNMhoIJsA//sK2uWoeqKO
pNd0nSrGPiQROiKQAnwa1GS4hDUD8JqdfDPAFpKyktI+4aOeDggkm+Ok3DRqF0E=
=gYxi
-----END PGP SIGNATURE-----

--------------enigE0C60527DF43D254995D96F6--

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

--===============0511264004==--