Am 11.01.2011, 22:44 Uhr, schrieb Tres Seaver tsea...@palladion.com:
Python 2.5 isn't even getting security fixes from Python devs now, which
means that Debian users are holding more risk than they know (I strongly
doubt the Debian packagers of Python are up for backporting all the
potential
Am 04.01.2011, 14:25 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu:
With the current roadmap, we'll
likely be able to stop using Zope 2.12 in 6-9 months altogether.
I've given this some thought: as long as Python 2.5 is the default install
on Debian-based systems, as it currently is, you
On Tue, Jan 11, 2011 at 7:58 PM, Charlie Clark
charlie.cl...@clark-consulting.eu wrote:
Am 04.01.2011, 14:25 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu:
With the current roadmap, we'll
likely be able to stop using Zope 2.12 in 6-9 months altogether.
I've given this some thought: as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/11/2011 02:05 PM, Hanno Schlichting wrote:
On Tue, Jan 11, 2011 at 7:58 PM, Charlie Clark
charlie.cl...@clark-consulting.eu wrote:
Am 04.01.2011, 14:25 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu:
With the current roadmap, we'll
Hi!
Zope trunk (2.14) no longer ships with these Products:
Products.BTreeFolder2
Products.ExternalMethod
Products.MailHost
Products.MIMETools
Products.PythonScripts
Products.StandardCacheManagers
There are no separate Zope 2.12 compatible eggs for these Products
because they
Hi and happy new year,
On Tue, Jan 4, 2011 at 2:00 PM, yuppie y.2...@wcm-solutions.de wrote:
Problem is: Several Products (e.g. CMF) exist that depend on these
Products and want to support Zope2 2.12, 2.13 and trunk.
Is that really needed? Zope 2.13 is stable now, 2.14 a couple months
away.
Hi Hanno!
Hanno Schlichting wrote:
With the mess of zope/zope.app distributions being part of Zope 2.12,
I'd really like to get people away from it and stop maintaining it
rather sooner than later. With Plone we are using CMF 2.2 and Zope
2.13 for the upcoming Plone 4.1. With the current
Hi Yvo.
On Tue, Jan 4, 2011 at 2:53 PM, yuppie y.2...@wcm-solutions.de wrote:
Using CMF 2.2 for Plone 4.1 means we have to maintain CMF 2.2 for a long
time and Zope 2.12 is the primary platform for CMF 2.2. So if you really
want stop maintaining Zope 2.12 soon: Wouldn't it be better to release
Hi!
Hanno Schlichting wrote:
On Tue, Jan 4, 2011 at 2:53 PM, yuppiey.2...@wcm-solutions.de wrote:
Using CMF 2.2 for Plone 4.1 means we have to maintain CMF 2.2 for a long
time and Zope 2.12 is the primary platform for CMF 2.2. So if you really
want stop maintaining Zope 2.12 soon: Wouldn't
On 4 January 2011 13:00, yuppie y.2...@wcm-solutions.de wrote:
Hi!
Zope trunk (2.14) no longer ships with these Products:
Products.BTreeFolder2
Products.ExternalMethod
Products.MailHost
Products.MIMETools
Products.PythonScripts
Products.StandardCacheManagers
There are no
On 4 January 2011 17:42, Laurence Rowe l...@lrowe.co.uk wrote:
On 4 January 2011 13:00, yuppie y.2...@wcm-solutions.de wrote:
Hi!
Zope trunk (2.14) no longer ships with these Products:
Products.BTreeFolder2
Products.ExternalMethod
Products.MailHost
Products.MIMETools
On Tuesday 04 January 2011, yuppie wrote:
Zope trunk (2.14) no longer ships with these Products:
Products.BTreeFolder2
Products.ExternalMethod
Products.MailHost
Products.MIMETools
Products.PythonScripts
Products.StandardCacheManagers
What will this mean for those of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/04/2011 02:24 PM, William Heymann wrote:
On Tuesday 04 January 2011, yuppie wrote:
Zope trunk (2.14) no longer ships with these Products:
Products.BTreeFolder2
Products.ExternalMethod
Products.MailHost
Products.MIMETools
13 matches
Mail list logo
