Dan - we are using 64bit Zope 2.8.7 and python 2.4 with no problems for
years now. It can do everything we want with regards to Python
scripting, database connectivity etc.
I can't think of any huge problems with staying on Zope 2.8.6/7 era. I
have said before 2.10+ breaks lots of products that would take ages to
hack about (especially for companies using Zope not individuals with
time on their hands). I'm all for upgrading, bug fixing and refactoring
normally, but the backwards compatibility with Zope makes it harder than
it should be.
On 08/12/10 12:11, Peter Bengtsson wrote:
> We're running several perfectly working 2.8 Zopes. They've been very stable.
> Annoying that Ubuntu insists on making Python 2.4 hard to install but
> for some of the servers we've changed back to Debian.
> On 7 December 2010 16:58, Dan Gaibel<d...@cornell.edu> wrote:
>> Good advice here, thanks! Is it a big mistake to stay at Zope 2.8.6? The
>> server has been very stable for years, apparently. What are the downfalls of
>> not upgrading all the way past 2.10?
>> On Dec 7, 2010, at 2:40 PM, Andrew Milton wrote:
>>> +-------[ Tres Seaver ]----------------------
>>> | -----BEGIN PGP SIGNED MESSAGE-----
>>> | Hash: SHA1
>>> | On 12/07/2010 01:18 PM, Dan Gaibel wrote:
>>> |> I have recently inherited the responsibility of supporting a fairly
>>> |> complex web server running Zope 2.8.6 on Python 2.3.5. This
>>> |> configuration is currently on a Linux (Fedora Core) server and I
>>> |> would like very much to migrate to OS X Server Snow Leopard. It also
>>> |> seems to me that I should consider upgrading Zope to a more current
>>> |> release while I'm at it. We heavily use MySQL and associated
>>> |> products, LocalFS, and the Python Imagining Library. We have a
>>> |> variety of ZClass homegrown products as well.
>>> |> I know that I'm in for a headache no matter what, but I wonder if any
>>> |> of you folks could point me in the right direction or offer advice on
>>> |> the situation. Is it crazy to jump from 2.8.6 to 2.12? Does anyone
>>> |> use OS X Server for Zope? Is this migration a mistake? Any pitfalls I
>>> |> should be looking out for?
>>> | I would do this in small steps, e.g. first migrate to the new machine /
>>> | - - Get Python 2.3.x installed on the OS/X server.
>>> | - - Build the latest Zope 2.8.* on that server.
>>> | - - Install and test products there in the same versions you now use.
>>> | - - Copy your old database over and test.
>>> | then upgrade the software stack:
>>> | - - Move carefully through the Zope releases (I would to 2.9, 2.10, and'
>>> | 2.12), upgrading Python as needed to stay on a supported version.
>>> | - - Check for upgrades to the products, and their compatibility with
>>> | Zope versions. Test them, and your site. after each upgrade.
>>> The move from 2.9 to 2.10 is likely to be the most painful part in
>>> terms of legacy Zope apps. A lot of products will break on 2.10
>>> Andrew Milton
>>> Zope maillist - Zope@zope.org
>>> ** No cross posts or HTML encoding! **
>>> (Related lists -
>>> https://mail.zope.org/mailman/listinfo/zope-dev )
>> Zope maillist - Zope@zope.org
>> ** No cross posts or HTML encoding! **
>> (Related lists -
>> https://mail.zope.org/mailman/listinfo/zope-dev )
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -