[ckan-committers] Officially dropping support for CKAN 1.7 and 1.8
nigel.babu at okfn.org
Mon Aug 18 02:45:34 UTC 2014
>From the sysadmin POV, the question is about shutting down infra we're not
using anymore. The existing repos will still exist but we won't be able to
provide updates for it easily after this shutdown.
Developer, Open Knowledge
On 15 August 2014 15:29, Adrià Mercader <adria.mercader at okfn.org> wrote:
> The friends at the sysadmin team make me notice that apt.ckan.org is
> already out of s031 and pointing to Amazon s3, so ignore all the
> server related stuff.
> The final question is, is everyone happy with us officially dropping
> support for 1.7 and 1.8?
> On 15 August 2014 10:27, Adrià Mercader <adria.mercader at okfn.org> wrote:
> > Hi all,
> > I just wanted to make sure that everyone is happy with me sending an
> > "official" email to the lists saying that 1.7.x and 1.8.x are no
> > longer supported. This has been the de-facto situation for a while,
> > the last time these branches were updated was last August due to a
> > patch for a *massive* security issue.
> > The reason I'm keen on moving this forward is that we've been asked to
> > decommission the server were the debian packages for these versions
> > were created (s031.okserver.org). This includes:
> > 1. The Jenkins instance that we used to create to deb packages
> > (http://s031.okserver.org:8080)
> > 2. The apt server that published them (http://apt.ckan.org/)
> > Migrating 1 to somewhere else would be a pain as it uses buildkit and
> > nobody knows how to set it up. I wonder if we somehow could we move 2
> > to another server in case someone is relying on those? @Nigel would
> > that be easy?
> > Or should we just shut the whole thing down?
> > Let me know your thoughts,
> > Adrià
> ckan-committers mailing list
> ckan-committers at lists.okfn.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ckan-committers