Attention Zope 3 KGS consumers: zope.kgs changes
Hi everyone, as you probably saw from the checkins last night, Paul and I finished all outstanding coding tasks that were blocking a Zope 3.4 release based on a KGS. In particular, we can generate a skinable Web site for a KGS and the release process is now very much automated. With these extensions comes also a change in URLs. All files/directories related to a particular version are now located within a directory named after the version. For the Zope 3 KGS, this will have the following impact: http://download.zope.org/zope3.4/versions-3.4.0c4.cfg -> http://download.zope.org/zope3.4/3.4.0c4/versions.cfg http://download.zope.org/zope3.4/controlled-packages-3.4.0c4.cfg -> http://download.zope.org/zope3.4/3.4.0c4/controlled-packages.cfg I will retroactively change the locations for all zope3.4 KGS releases. Thus, I am very interested to hear from the consuming communities: How painful is that for you? I am particularly interested to hear from Grok, Zope 2 and Plone, but also from individuals using the KGS. Thanks! Regards, Stepan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
Stephan Richter wrote: [snip]
I will retroactively change the locations for all zope3.4 KGS releases.
Thus, I am very interested to hear from the consuming communities: How painful is that for you? I am particularly interested to hear from Grok, Zope 2 and Plone, but also from individuals using the KGS.
Shouldn't make a difference for Grok, as we really maintain our own list but synch with KGS's list once every while. Regards, Martijn
On Tuesday 27 January 2009, Martijn Faassen wrote:
Shouldn't make a difference for Grok, as we really maintain our own list but synch with KGS's list once every while.
Great. So I think I will switch the KGS tonight, so that you all can see the results of the work we did. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
Stephan Richter wrote:
I will retroactively change the locations for all zope3.4 KGS releases.
Thus, I am very interested to hear from the consuming communities: How painful is that for you? I am particularly interested to hear from Grok, Zope 2 and Plone, but also from individuals using the KGS.
Plone doesn't use the Zope 3.4 KGS in any way. Our most current version stable version Plone 3.2 has moved to an egg-based install, with the exception of Zope2 and everything it includes. Thus we still rely on the Zope2 old-style full tarball release. For current Plone 4.0 / trunk we are aiming at Zope 2.12 /trunk whose eggification is almost complete. This is based on the version set specified in the Zope 3.4 KGS. The technical means by which it does that, is however having a local copy of the versions.cfg from http://download.zope.org/zope3.4/versions.cfg. So changing URL's doesn't cause any problems for us. I think I can speak for both the Plone and Zope2 project here. Hanno
On Tuesday 27 January 2009, Hanno Schlichting wrote:
For current Plone 4.0 / trunk we are aiming at Zope 2.12 /trunk whose eggification is almost complete. This is based on the version set specified in the Zope 3.4 KGS. The technical means by which it does that, is however having a local copy of the versions.cfg from http://download.zope.org/zope3.4/versions.cfg. So changing URL's doesn't cause any problems for us.
I think I can speak for both the Plone and Zope2 project here.
Great. Thanks. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
On Tue, Jan 27, 2009 at 18:57, Stephan Richter <srichter@cosmos.phy.tufts.edu> wrote:
as you probably saw from the checkins last night, Paul and I finished all outstanding coding tasks that were blocking a Zope 3.4 release based on a KGS. In particular, we can generate a skinable Web site for a KGS and the release process is now very much automated.
Great! Is there any reason to not upload zope.kgs and zope.release to Pypi? -- Sebastien Douche <sdouche@gmail.com>
On Wednesday 28 January 2009, Sebastien Douche wrote:
On Tue, Jan 27, 2009 at 18:57, Stephan Richter
<srichter@cosmos.phy.tufts.edu> wrote:
as you probably saw from the checkins last night, Paul and I finished all outstanding coding tasks that were blocking a Zope 3.4 release based on a KGS. In particular, we can generate a skinable Web site for a KGS and the release process is now very much automated.
Great! Is there any reason to not upload zope.kgs and zope.release to Pypi?
Nope, I will do that soon. I was just concentrating on the Zope 3.4 release first. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
On Tue, Jan 27, 2009 at 09:57:49AM -0800, Stephan Richter wrote:
With these extensions comes also a change in URLs. All files/directories related to a particular version are now located within a directory named after the version. For the Zope 3 KGS, this will have the following impact:
http://download.zope.org/zope3.4/versions-3.4.0c4.cfg -> http://download.zope.org/zope3.4/3.4.0c4/versions.cfg
http://download.zope.org/zope3.4/controlled-packages-3.4.0c4.cfg -> http://download.zope.org/zope3.4/3.4.0c4/controlled-packages.cfg
I will retroactively change the locations for all zope3.4 KGS releases.
Can you add Apache rewrite rules to redirect the old URLs to the new locations, just on general principles ("cool URLs don't change")? Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
On Wednesday 28 January 2009, Marius Gedminas wrote:
Can you add Apache rewrite rules to redirect the old URLs to the new locations, just on general principles ("cool URLs don't change")?
If someone with sys admin rights helps me, sure. On the other hand, now that I think about it, I wonder whether symlinks would work too. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stephan Richter wrote:
On Wednesday 28 January 2009, Marius Gedminas wrote:
Can you add Apache rewrite rules to redirect the old URLs to the new locations, just on general principles ("cool URLs don't change")?
If someone with sys admin rights helps me, sure. On the other hand, now that I think about it, I wonder whether symlinks would work too.
If Apache is configured to follow them, yes. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJgOLN+gerLs4ltQ4RAsRdAJ9jn0hnbqNFO2TfAioJuQZlQkWJKQCeJvij FhW+l9TQYNowhQ9FGt1xgbA= =uUdg -----END PGP SIGNATURE-----
participants (6)
-
Hanno Schlichting -
Marius Gedminas -
Martijn Faassen -
Sebastien Douche -
Stephan Richter -
Tres Seaver