On 10/18/2011 10:54 AM, M.-A. DARCHE wrote: > Hello :-) > > Le 17/10/2011 19:34, Georges Racinet a écrit : >> [...] >> About version numbers, I am more and more convinced that 3.6 should stay >> on Zope 2.10, support the current distribution standard (eggs + >> buildout) plus a few nice features.
The porting to CMF 2.1.1 is now considered done (see http://trac.cps-cms.org/ticket/2453). In particular, the periodic test runs now include the default branch for CPS-3-base and CPS-3 (a.k.a Standard). Obviously there's still a bit of cleaning to be made, and some legacy stuff (mostly related to CPSSkins) to be reorganized. To get back on the subject of version numbers, I'm wondering if we could release an early 3.6.0 with just that, start the eggification with 3.6.1, etc ? The alternative would be to tag 3.6.0 once every component in CPS-3-full works and is available on pypi. Opinions ? -- 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
