Re: Zope version cfgs

Hi Eric,

any progress on this?

Looks like 4.3.3-pending/versions.cfg si broken since it finds

http://dist.plone.org/release/4.3.3-pending/zopeapp-versions.cfg

but not

http://dist.plone.org/release/4.3.3-pending/zope-versions.cfg

Maybe you forgot one? :)

Thanks!
S.



On Sat, Feb 22, 2014 at 1:39 AM, Eric Steele <[email protected]> wrote:

> On 21 Feb 2014, at 19:09, Maurits van Rees wrote:
>
> Eric Steele schreef op 22-02-14 00:51:
>
> How do we want to handle referencing zope/zopeapp/ztk versions.cfg files
> now that downloads.zope.org is no longer hosting them? Right now, we've
> got the cfgs for the latest tags in the 4.3.3 and 5.0 buildouts with the
> thought of putting them into the relevant release folders at
> http://dist.plone.org/release/.
>
> What seems like the better option would be to pull in the old ones as
> well and host them all somewhere on dist.plone.org. This gets them
> behind our CDN and helps out those running older releases of Plone. Is
> there any reason we couldn't do that? Is anyone willing to own this
> task?
>
> Eric
>
> Is download.zope.org really no longer hosting them or is it scheduled to
> stop servicing those requests? It seems good at the moment.
>
> You mention downloads.zope.org (plural) which is not available. But
> note that there is downloads.buildout.org (plural) and download.zope.org
> (singular) which are both available. So I wonder if this is simply a
> mixup between two domain names.
>
> It could be good to host these files ourselves, to avoid problems when
> download.zope.org really is down. It is one server less that needs to
> be up for some buildouts to finish correctly.
>
> BTW, I have a small script that reads a buildout config file, parses the
> extends lines and downloads them:
> https://gist.github.com/mauritsvanrees/1097587
> I use that to download the extends of the plone versions.cfg for the
> Plone version that a client buildout is using and I put those files in
> version control so the buildout does not need to go online for those
> extends lines.
>
> Cheers,
>
> --
> Maurits van Rees: http://maurits.vanrees.org/
> Zest Software: http://zestsoftware.nl
>
> Sorry, I meant download.zope.org. According to this email from Hanno in
> June <http://plone.293351.n2.nabble.com/download-zope-org-td7566681.html>,
> "... the Zope infrastructure team has decided to discourage relying on
> download.zope.org for production deployments...The next Zope 2 releases
> won't be available from download.zope.org anymore, so coredev and any
> release machinery should probably be adjusted."
>
> So, old ones are still there, but the latest Zope2 release, 2.13.22, is
> not. Currently the cfgs for that live in GitHub tags<https://github.com/zopefoundation/Zope/blob/2.13.22/versions.cfg>and in our
> coredev buildout<https://github.com/plone/buildout.coredev/commit/eee10225facad6abc9d96c892660ac40ec2d13f6>.
> In the process of releasing 4.3.3, I've added that to the release
> directory on dist.plone.org<http://dist.plone.org/release/4.3.3-pending/zope-versions.cfg>.
>
>
> So the question is really this: From this point forward, we need to host
> the version pins for any new Zope releases that Plone uses. Since we have
> the infrastructure in place to do so in a far more stable manner, should we
> host the old ones as well?
>
> Eric
>
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
> _______________________________________________
> Plone-developers mailing list
> Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/plone-developers
>
>

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers