CPS 3.5.3 tagged, new policy for ticket milestones

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

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig18A2CB5903C38F3C40BB7722
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Greetings

CPS 3.5.3 has been tagged last night (CEST). We still need tarballs and
debian packages to call that a release.

CPS BRANCHES
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The new CPS-3.5 branch has been created right afterwards and is now
considered stable, CPS-3.4 is not supported anymore.

What 'stable' actually means has to be refined, but let's say for the
time being that it implies that no evolution with great impact on the
core components (CPSCore, CPSSchemas, CPSWorkflow=85) shall be accepted.

The default branch is now called CPS 3.6.0-dev, and is primarily
dedicated to catch up with Zope >=3D 2.12 versions (deprecation warnings
hunt is open)

We hope the new policy about ticket milestones in the trac will allow us
to release more often. The problem is that we have lots of old tickets,
of which many are still relevant in some way. This wastes lost of time
right before the tagging, since we have to inspect tickets and mark
those that were just waiting for confirmation to be closed.

NEW MILESTONE POLICY
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

all tickets that were related to the 3.5.3 milestone have been
automatically reported to 3.5.5. Therefore, 3.5.4 only has a few
tickets, and we'll release it as soon as they are done.

Developers can still cherry-pick some of the 3.5.5 tickets, reassign
them to 3.5.4 and treat them. We can also already postpone some tickets
from 3.5.5 to 3.5.6.
At the time of the 3.5.4 release, all tickets assigned to 3.5.5 will be
postponed to 3.5.6 and so on.

Of course, this makes sense only because we expect new tickets to be
registered for 3.5.4 in the meanwhile, and the volume of such new
tickets is expected to be roughly the same as for older ones.

Cheers,

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


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

iQEcBAEBCAAGBQJOfFjRAAoJEOAffZJiF+Z4rZcIAOR+IGq+X6io4y2yl1jA00Ys
59yMyv0qgCywla/yQuaLVvENFJXp41jM+GU1rwOSSv1nuolR2g8n4ESxjTiv8zFq
TWDfBKbUNZSg12phDFre8XwTE/LTg3pwNDurtPnCOYGVdT7dveXIedlROE2LPafZ
q+68sQtlczcNqmv0d2QUinKTkz1UeN4IV3qB/vr+blBUbJLqzGxVdM19fVwNN2L9
8ttqLCZKLNyeJ/Tyg8vId5+qRpOsOaYbBLV5EbK0CAsAUcBnDbKaNo9fOnwE3jSV
TCv67lJifvV8u23uV2n7e56Vng5zL6/KiJCOEGpOUM9p5u8y/IakmSk7xScvxQU=
=lkPc
-----END PGP SIGNATURE-----

--------------enig18A2CB5903C38F3C40BB7722--

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

--===============1184634965==--