CKAN: Ticket #1591: Upgrade CKAN 1.5 instances

description changed

dread — Thu, 22 Dec 2011 12:11:39 GMT

description modified (diff)

description changed

dread — Thu, 22 Dec 2011 12:43:53 GMT

description modified (diff)

description changed

dread — Thu, 22 Dec 2011 12:44:54 GMT

description modified (diff)

description changed

dread — Wed, 04 Jan 2012 19:21:47 GMT

description modified (diff)

Today I upgraded s057: br cz ie norway

owner, status, description changed; cc set

dread — Thu, 05 Jan 2012 11:49:56 GMT

cc thejimmyg added
owner changed from dread to icmurray
status changed from new to assigned
description modified (diff)

I've now completed the upgrade for datacatalogs.org. All that remains now is DGU. Reassigning to Ian as I'm away shortly.

rgrp — Fri, 06 Jan 2012 16:10:29 GMT

Report of time spent / time estimate would be brilliant :-)

dread — Mon, 09 Jan 2012 13:59:28 GMT

Spent about one day on this from myself.

milestone changed

icmurray — Thu, 12 Jan 2012 19:05:17 GMT

milestone changed from ckan-sprint-2012-01-09 to current-ckan-sprint-2012-01-23

keywords set

icmurray — Thu, 12 Jan 2012 19:14:41 GMT

keywords 1d added

status changed; resolution set

rgrp — Mon, 23 Jan 2012 11:15:21 GMT

status changed from assigned to closed
resolution set to fixed

Done. (DGU waiting on integration)

dread — Mon, 23 Jan 2012 12:03:29 GMT

All covered off. DGU is 1.5 but security issue fixed previously.

cc, status changed; resolution deleted

nils.toedtmann — Wed, 08 Feb 2012 21:17:29 GMT

cc rgrp, nils.toedtmann added
status changed from closed to reopened
resolution fixed deleted

Some critical CKANs (e.g. PDEU, DataNL, DataGM) seem to be still on pre-1.5 versions. Shouldn't they be upgraded too? Or is that tracked elsewhere?

status changed; resolution set

dread — Thu, 09 Feb 2012 12:11:10 GMT

status changed from reopened to closed
resolution set to fixed

This ticket was created in response to the security issue in CKAN 1.5 only - it does not affect other versions.

There is a different argument to upgrade older CKANs installed elsewhere, but there tend to be problems with extensions and themes not being compatible, so I think should be considered on a case-by-case basis and how much budget is available.