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 ============ 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…) shall be accepted. The default branch is now called CPS 3.6.0-dev, and is primarily dedicated to catch up with Zope >= 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 ==================== 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, -- Georges Racinet, http://www.racinet.fr, http://anybox.fr Zope/CPS & OpenERP expertise, assistance & development GPG: 0x4862FFF7 identi.ca & twitter: gracinet
signature.asc
Description: OpenPGP digital signature
_______________________________________________ cps-devel mailing list http://lists.nuxeo.com/mailman/listinfo/cps-devel
