-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hanno Schlichting wrote: > Tres Seaver wrote: >> Hanno Schlichting wrote: >>> Here's a list of things I'd like to see in a 2.12 release: >>> - Official Python 2.5 and 2.6 support (almost done, requires a community >>> decision on when we call RestricedPython supported and reviewed) >> +1 for 2.5; I'm pretty sure 2.6 is not there yet, and may be too hard >> to aim for in one release. > > Let me explain why I'd like to aim for Python 2.6 as a supported version > from a Plone perspective. > > Plone's roadmap including true major versions looks like this: > > 1.0 - February 2003 > 2.1 - September 2005 > 3.0 - August 2007 > 4.0 - maybe late 2009 > 5.0 - not likely before 2011 > > My guesstimate says, we are going to release major new versions about > every two years. This is a wild guesstimate but the best I have today. > In addition I don't see us moving to new Python versions outside of > those major version changes. > >>From my point of view it is desirable for us to be able to run Plone 4.0 > based on Python 2.6 in about a year and use it as a stable version > throughout 2010 and 2011. > > By that time we will be three years after the release of Python 3. I'd > like to be able to use those years to prepare our codebase for Python 3 > and have a possibility to use it for Plone 5. Python 2.6 will give us > the chance of preparing for that move. > > Maybe I'm going to be wrong and we will move to yearly major releases, > maybe Plone dies, Python 3 is not adopted by anyone. All possible, but > based on the knowledge I have today, not moving to Python 2.6 for the > next major Plone version will leave us behind in a Python world, which > has moved on.
I'm fine with having Plone 4 able to run on a 2.6-compatible Zoep2. If we add Python 2.6 to the supported list for a no-later-than Q3 2009 Zope release, that should be sufficient, no? >>From a Zope perspective 2.11 should have had Python 2.5 support, but > nobody cared enough to make it happen. We can support Python 2.4 and 2.5 > alone in Zope 2.12 and release it in the next months. We should do a 2.12 very soon (before year end, likely), and it should retain 2.4 compatibility. > In that case Plone will neither use 2.11 nor 2.12 but go straight for a > Zope 2.13 including Python 2.6. A major release every six month would be > desirable for us in that case. Right now I don't see anyone, who would > be using those releases. If those people exist, please speak up. Plone isn't the only consumer of Zope2, although it is clearly the biggest one. Keeping an orderly succession of releases with good compatibility is important for the whole ecosystem (frankly, Plone should be willing to move to newer Zope versions even in a second dot release, but that is another debate). Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJChvx+gerLs4ltQ4RAm+nAJ9PwVjy4zOSXotiJafe/HYejjLH0wCcDFqC P8lcNefTAIZ1eVF6DHWx3Dc= =eFP2 -----END PGP SIGNATURE----- _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
