Mailing List Archive

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/04/2016 08:27 AM, Michael Brunnbauer wrote:
>
> hi all,
>
> I used to watch https://pypi.python.org/pypi/Zope2/ for Zope 2
> updates. Last version I updated to was 2.13.24.
>
> Now this page offers version 4.0a2 - the a indicating alpha status -
> but
>
> https://zope.readthedocs.io/en/2.13/CHANGES.html
>
> announces an unreleased version 2.13.25. What does this mean?
>
> Does Zope 2 still receive security updates? How can I stay informed?

Yes, it still receives them. The 4.0a2 release you are seeing is part of
an ongoing "refresh Zope2" effort, driven by the Plone community and
friends. The 2.13.25 release you see in the docs hasn't yet been made:
your options to get to a supported state include a) running from the head
of the 2.13 branch (super stable at this point); or b) applying the
various hotfixes released by the Plone folks:

https://plone.org/security/hotfixes


Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJX9A9wAAoJEPKpaDSJE9HYrFEP/3ZV8ehXZBtb9TKMurW7HmGA
trKAs+gGOLru7HUIYohDpCTOyaKTsXpvNAR/y1UmX+jULe0aAzThde6zt26WlYbH
XnkysCxOIdhb+PicE0ZfAOKKJPg83AKkaW83BaUFuwBkfZyW4g3guW79Qiv9V1VD
clam4WG04O4hKzFBx00yfwhbekNRsBKQ1PZvWN0bi5eVoVssurNGbwZamOOiJ24e
jvzYTDlT3FhUW9vUyAG84lOdXRQJtx/SSJk37RzBBE51CvjWfgcsJ3R1IcelI16Z
fnBm5LfjHXuwW+kVQF0FpIfrKQzgy2/gozDqaSk+4M1y2G6dmfyTi5z7FU1Dmv83
5tgbAZHOCxokhz+zq/kdVdADYqEFTjVl28r+ijv9yDBpODBUnNZxyFHtb4wfVLHL
VhWHis3AnejJDJIoPgDMM0RGI6wN4Dfv3+ndd7tgFppOwozmKslvKsJr+SDDhFA5
YMcSTKRqdroHm6NXKQrdL3OV39aZaDVNZqUY16ACoSgdpmJxDqtnadGC34lzHZfs
pEviG0DwZ6KWxVc0fWtE5O1+cco/kCsmH080V1O+GJKfg8LMvp9ehUiOtPUCl8ec
BDoJFvBhHcDBedWQ9wchg95YxloF5V3QCX9he/XL3AXUI6+F25zrbPu/9pK/b2ED
4v7mtFyoFXtpeVGA22uW
=kAh3
-----END PGP SIGNATURE-----

_______________________________________________
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 )

2016-10-04 7:27 GMT-05:00 Michael Brunnbauer <brunni@netestate.de>:

>
> hi all,
>
> I used to watch https://pypi.python.org/pypi/Zope2/ for Zope 2 updates.
> Last
> version I updated to was 2.13.24.
>
> Now this page offers version 4.0a2 - the a indicating alpha status - but
>
>
I think this break the intention of
https://zope.readthedocs.io/en/latest/WHATSNEW.html#version-numbering-increase
The package should be https://pypi.python.org/pypi/Zope4/




--
________________________________________
Lo bueno de vivir un dia mas
es saber que nos queda un dia menos de vida

Hello Johannes,

On Tue, Nov 01, 2016 at 01:03:09AM -0500, Johannes Raggam wrote:
> Still, the 2.13 branch is still being used and security-patched.

Great! What is the URL I watch for updates - the home of the 2.13 branch?

Regards,

Michael Brunnbauer

--
++ Michael Brunnbauer
++ netEstate GmbH
++ Geisenhausener Straße 11a
++ 81379 München
++ Tel +49 89 32 19 77 80
++ Fax +49 89 32 19 77 89
++ E-Mail brunni@netestate.de
++ http://www.netestate.de/
++
++ Sitz: München, HRB Nr.142452 (Handelsregister B München)
++ USt-IdNr. DE221033342
++ Geschäftsführer: Michael Brunnbauer, Franz Brunnbauer
++ Prokurist: Dipl. Kfm. (Univ.) Markus Hendel

2016-11-07 1:18 GMT-06:00 Michael Howitz <mac@gmx.net>:

> Am 04.10.2016 um 22:39 schrieb Miguel Beltran R. <yourpadre@gmail.com>:
> > 2016-10-04 7:27 GMT-05:00 Michael Brunnbauer <brunni@netestate.de>:
> […]
> >> Now this page offers version 4.0a2 - the a indicating alpha status - but
> >
> > I think this break the intention of https://zope.readthedocs.io/en
> /latest/WHATSNEW.html#version-numbering-increase
> > The package should be https://pypi.python.org/pypi/Zope4/
>
> Why do you think we need a rename of the package?
>
>
>
> --
> Mit herzlichen Grüßen
> Michael Howitz
>
>
Because the package name https://pypi.python.org/pypi/zope doesn't exists,
actually is using the number version (https://pypi.python.org/pypi/zope2)

Also
Zope4 break/drop compatibility with Zope 2
The page says it's version 4
Break the installion using pip install -r https://raw.githubusercontent.
com/zopefoundation/Zope/2.13.24/requirements.txt (see my other email)
<https://raw.githubusercontent.com/zopefoundation/Zope/2.13.24/requirements.txt>



--
________________________________________
Lo bueno de vivir un dia mas
es saber que nos queda un dia menos de vida

Am 07.11.2016 um 19:18 schrieb Miguel Beltran R. <yourpadre@gmail.com>:
> 2016-11-07 1:18 GMT-06:00 Michael Howitz <mac@gmx.net>:
> > Why do you think we need a rename of the package?
>
> Because the package name https://pypi.python.org/pypi/zope doesn't exists, actually is using the number version (https://pypi.python.org/pypi/zope2)
>
> Also
> Zope4 break/drop compatibility with Zope 2
> The page says it's version 4
> Break the installion using pip install -r https://raw.githubusercontent.com/zopefoundation/Zope/2.13.24/requirements.txt (see my other email)

You are right, it might look strange to have a Zope2 version 4.x.
But renaming the Package on PyPI would cause problems for all packages which depend on Zope 4.x, especially for the ones which are even compatible with Zope 2.x and 4.x.

@Hanno: What do you think about renaming the PyPI package to Zope?


--
Mit freundlichen Grüßen
Michael Howitz

2016-11-11 5:20 GMT-06:00 Hanno Schlichting <hanno@hannosch.eu>:

> On Thu, Nov 10, 2016, at 09:12, Michael Howitz wrote:
> > You are right, it might look strange to have a Zope2 version 4.x.
> > But renaming the Package on PyPI would cause problems for all packages
> > which depend on Zope 4.x, especially for the ones which are even
> > compatible with Zope 2.x and 4.x.
>
> I agree that having the project/distribution name as Zope2 and the
> version as 4.x, 5.x, etc. isn't ideal.
>
> But by now there are probably hundreds of other projects, which depend
> on Zope2 in their setup.py. Not to mention all kinds of buildout files,
> testing configurations or tools, the configuration for sites like
> https://zope3.pov.lt/py3/ and many other things we don't know about.
>
> > @Hanno: What do you think about renaming the PyPI package to Zope?
>
> I think this is a cosmetic change, which at this point causes too much
> work and breakage for very little gain.
>
> Hanno
>

And why not start a new package call "zope" (in PyPi) that it's really
version 4. it's alpha version so no many projects are using it.

--
________________________________________
Lo bueno de vivir un dia mas
es saber que nos queda un dia menos de vida

Am 11.11.2016 um 19:42 schrieb Miguel Beltran R. <yourpadre@gmail.com>:
> And why not start a new package call "zope" (in PyPi) that it's really version 4. it's alpha version so no many projects are using it.

As mentioned earlier in this thread: This would it make nearly impossible to support both Zope 2.x and Zope 4.x in a single release of a third party package using Zope. Requiring separate releases for Zope 2 and Zope 4 is painful enough for the Zope core itself. Requiring this for the whole ecosystem would decrease the chance of Zope 4 to be used at all.

--
Mit freundlichen Grüßen
Michael Howitz