RE: [Zope-dev] Why not ZODB 3.1.3 with Zope 2.6.2?

2003-08-27 Thread Tim Peters
[Paul Winkler] I downloaded the hidden 2.6.2b6 release (from http://zope.org/Products/Zope/2.6.2b6/Zope/view) and had a look in lib/python/ZODB/__init__.py, which gives its version as ZODB 3.1.2. Is there any reason it's not ZODB 3.1.3? Because 3.1.3 hasn't yet been tested with that

[Zope-dev] upgrading and getting rid of SearchIndex

2003-08-27 Thread Anthony Baxter
I've got a couple of ZODBs here that's been gradually upgraded over time from Zope version to Zope version (I think they were initially started on Zope 1.x!) I'm sick of the SearchIndex deprecation warnings, so I've gone and re-created all of the catalog indexes. This fixed it for the indexes,

Re: [Zope-dev] Zope 2.7 Timeline

2003-08-27 Thread Joachim Werner
Hi! WRT the Zope 2.7 timeline: Couldn't we just get a new beta that includes the most critical bug fixes very soon? If 2.7 doesn't get deployed on almost production systems there will not be too much further testing I guess. And currently most non-experts will not even be able to get a Zope

Re: [Zope-dev] Zope 2.7 Timeline

2003-08-27 Thread Chris McDonough
2.7.0b2 was released yesterday with both of these bugs fixed. Is that soon enough? ;-) On Wed, 2003-08-27 at 05:42, Joachim Werner wrote: Hi! WRT the Zope 2.7 timeline: Couldn't we just get a new beta that includes the most critical bug fixes very soon? If 2.7 doesn't get deployed on

Re: [Zope-dev] Zope 2.7 Timeline

2003-08-27 Thread Joachim Werner
Chris McDonough wrote: 2.7.0b2 was released yesterday with both of these bugs fixed. Is that soon enough? ;-) Yes it is ;-) Sorry, I didn't check before ... ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev **

Re: [Zope-dev] Very severe memory leak

2003-08-27 Thread Leonardo Rochael Almeida
On Mon, 2003-08-25 at 23:35, Shane Hathaway wrote: On 08/25/2003 05:12 PM, Leonardo Rochael Almeida wrote: Let me restate something important, because I forget about it myself sometimes when I'm thinking about this problem: *upgrading to 2.6.1 made the situation definetly worse*. The site