[Zope-CMF] Re: RFC: backporting including python-package-product support to support Zope 2.8

2006-01-18 Thread Philipp von Weitershausen
Martin Aspeli wrote: From what you're saying I deduct that Plone 2.1 favours Zope 2.7 over 2.8. Below you are suggesting that Plone 2.5 should do the same with Zope 2.8 (favouring it over 2.9). I don't understand why that should be. If one version has to be favoured at all, it should be

[Zope-CMF] CMF Collector: Open Issues

2006-01-18 Thread tseaver
The following supporters have open issues assigned to them in this collector (http://www.zope.org/Collectors/CMF). Assigned and Open jens - Discussion replies removal, [Accepted] http://www.zope.org/Collectors/CMF/391 - 'CMF Default Workflow [Revision 2]' Extension broken,

[Zope-CMF] Re: RFC: backporting including python-package-product support to support Zope 2.8

2006-01-18 Thread Raphael Ritz
Philipp von Weitershausen wrote: [..] except perhaps if he wants to get started right now, with Plone 2.1 (though that might still run under Zope 2.9 and CMF 1.6, I hope). Well, I was tinkering a little bit with Plone 2.1 on Zope 2.9 (or the Plone-2.1 bundle to be precise) not too long ago and

[Zope-CMF] Re: RFC: backporting including python-package-product support to support Zope 2.8

2006-01-18 Thread Raphael Ritz
Raphael Ritz wrote: Philipp von Weitershausen wrote: [..] except perhaps if he wants to get started right now, with Plone 2.1 (though that might still run under Zope 2.9 and CMF 1.6, I hope). Well, I was tinkering a little bit with Plone 2.1 on Zope 2.9 (or the Plone-2.1 bundle to be

[Zope-CMF] Re: using effective date to replace content?

2006-01-18 Thread martin f krafft
also sprach Raphael Ritz [EMAIL PROTECTED] [2006.01.18.1004 +0100]: Traditionally I think most people use cron for that (call 'zopectl run my-update-script' assuming you are using ZEO). Yeah, I know about that, but it requires filesystem access, which is not very scalable IME. Alternatively,

[Zope-CMF] Re: DeprecationWarnings for container events

2006-01-18 Thread Florent Guillaume
Tres Seaver wrote: I'd like to get the CMF-trunk clean of Deprecation warnings, at least when running unit tests or starting up Zope, and those emitted by OFS.subscribers are the remaining ones I know about. How do you mean for objects to handle the case where *they* need to respond to

[Zope-CMF] Re: RFC: backporting including python-package-product support to support Zope 2.8

2006-01-18 Thread Alexander Limi
On Wed, 18 Jan 2006 00:45:14 -0800, Philipp von Weitershausen [EMAIL PROTECTED] wrote: Let's put it this way: By the time Plone 2.5 is releases (if according to roadmap), Zope 2.8 is one month away from being *discontinued*. Conservative or not, I wouldn't bet on a release line that won't

[Zope-CMF] Re: [z3-five] Re: RFC: backporting including python-package-product support to support Zope 2.8

2006-01-18 Thread Andreas Jung
--On 18. Januar 2006 09:03:15 -0800 Alexander Limi [EMAIL PROTECTED] wrote: Note that I'm not saying it *won't* ship with 2.9, just that we reserve the right to ship with 2.8, since the 2.9 status is still uncertain, What is uncertain (except the issues with the Windows release)? -aj

[Zope-CMF] Re: [z3-five] Re: RFC: backporting including python-package-product support to support Zope 2.8

2006-01-18 Thread Andreas Jung
--On 18. Januar 2006 09:30:37 -0800 Alexander Limi [EMAIL PROTECTED] wrote: On Wed, 18 Jan 2006 09:20:41 -0800, Andreas Jung [EMAIL PROTECTED] wrote: --On 18. Januar 2006 09:03:15 -0800 Alexander Limi [EMAIL PROTECTED] wrote: Note that I'm not saying it *won't* ship with 2.9, just that we

Re: [Zope-CMF] Re: RFC: backporting including python-package-product support to support Zope 2.8

2006-01-18 Thread Philipp von Weitershausen
Andrew Veitch wrote: Let's put it this way: By the time Plone 2.5 is releases (if according to roadmap), Zope 2.8 is one month away from being *discontinued*. Conservative or not, I wouldn't bet on a release line that won't receive bugfixes the minute I start using it... Just so I'm clear,