Mailing List Archive

On 2/12/19 3:27 PM, Jesus Cea wrote:
> With less than a year away until Python 2.7 becomes "deadware", I wonder
> about the plan.
>
> I am using Zope 2.13 under Python 2.7. Huge sites with ZODB sizes in the
> multi gigabyte range. A handful of custom classes I could rewrite in
> Python 3 if needed.
>
> Is there any best practices I should be aware/follow to survive after
> Python 2.7 demise?. How long will be Zope2 2.13 be alive after that?.
> What about migration plans to Zope 4?
>
> Of course, I know that Python 2.7 interpreter will not suddenly die 1st
> January 2020. Just wondering if there is a ZOPE roadmap migration or if
> it will be a procedure each of us will need to overcome alone.
>
> Thanks for like 22 years of great service, so far :). That is very
> appreciated, whatever happens.


Hear hear!

Zope2 still running merrily at http://zwiki.org , for what it's worth.
(Zope 2.13.5, python 2.6.6)

Best,
-Simon


_______________________________________________
Zope maillist - Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope-dev )

Hi Jesus,

maybe you are not aware of it, but Zope 4 runs both on Python 2.7 and
3.4+.

So, the recommended upgrade path would be something like this:
- update to the latest 2.13 version
- update to Zope 4 on Python 2
- update to Zope 4 on Python 3 (which makes ZODB conversion necessary)

I do not think there are fixed dates when support for old versions get
dropped - ususally the Zope support is coupled to the Plone support - so
if any supported Plone version needs a special Zope version, Zope gets
supported.

You are definitely not on your own. There are Zope 4 sprints hosted by
gocept (Halle/Saale, Germany), where you could take part, both
contribute and learn about what to do. The next one is in May.
https://twitter.com/gocept/status/1082200091199524864

Also, if you cannot do the upgrade yourself, there are some companies
out there which can do that for you.

There is quite some information out there about upgrade paths for Python
software in general, but also especially for the Zope/Plone context
(blog of gocept.net, starzel.de, https://zope.readthedocs.io/en/latest/

There are only so and so many Zope developers out there, so I would not
bet on a long term maintenance of 2.13.

--
Jürgen Gmach . juergen.gmach@apis.de . +49 9482 941545
APIS Informationstechnologien GmbH . https://www.apis.de
Gewerbepark A 13, 93086 Wörth/Donau . Deutschland
Sitz der GmbH: Wörth/Donau, Amtsgericht Regensburg (HRB 6684)
Geschäftsführer: Julia Anna Dietz, Jürgen Eilers, Peter Rosenbeck
_______________________________________________
Zope maillist - Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope-dev )

Hi Jesus,

Am 13.02.2019 um 00:27 schrieb Jesus Cea <jcea@jcea.es>:
> With less than a year away until Python 2.7 becomes "deadware", I wonder
> about the plan.

I am currently maintaining the Zope releases, so the plan currently looks like the following:

* Zope 2.13 gets security fixes and maybe contributed bugfixes as long as there is a Plone version which supports it.
The last Plone version supporting Zope 2.13 is Plone 5.1. Currently the last two major releases of Plone are officially supported.
So with the final release of Plone 7 there is no more need for Zope 2.13 support. (Plone 5.2 is going to its beta stage now.)

* Zope 4 is the successor of Zope 2.13 supporting both Python 2.7 and Python 3.
I plan to have a final release this year. Zope 4 is already stable enough to use it. union.cms is running live on Zope 4.0b8 for a quite large installation.

* Zope 4 will not be a long-term supported release. We are planning to start working on Zope 5 in 2020. Zope 5 will drop Python 2 support and deprecated functions and imports.
This means the code in Zope which is currently needed to support Python 2 will be removed, so it actually cannot be run on Python 2 at all.

* So Zope 4 is the release to should jump on to get the train to Zope 5 and to al long-term supported release running on Python 3.

I think a should write this thoughts into a blog post, maybe this will reach a broader audience.

--
Mit freundlichen Grüßen
Michael Howitz