[ckan-dev] New config properties and upgrade version

Florian.Brucker at it.karlsruhe.de Florian.Brucker at it.karlsruhe.de
Tue Sep 5 10:19:41 UTC 2017


I've created a ticket: https://github.com/ckan/ckan/issues/3799

@Adria: Feel free to assign it to me.


Regards,
Florian


"ckan-dev" <ckan-dev-bounces at lists.okfn.org> schrieb am 05.09.2017 
11:56:26:

> Von: Adrià Mercader <adria.mercader at okfn.org>
> An: CKAN Development Discussions <ckan-dev at lists.okfn.org>, 
> Datum: 05.09.2017 11:56
> Betreff: Re: [ckan-dev] New config properties and upgrade version
> Gesendet von: "ckan-dev" <ckan-dev-bounces at lists.okfn.org>
> 
> Hi,
> 
> Florian is correct, we should have listed this in the changelog. We 
> can still change the one on master and backport the changes to the 
> next patch release so they come up in the CHANGELOG on docs.ckan.org.
> 
> Adrià
> 
> On 5 September 2017 at 10:10, <Florian.Brucker at it.karlsruhe.de> wrote:
> Dear David, 
> 
> I also think that this should be documented. We try to keep the 
> update-guide you linked to as general as possible, so that it works 
> for all versions of CKAN. Therefore, a better place for documenting 
> new or changed configuration options would be the change log [0], 
> which already lists other important changes, such as required 
> database upgrades. The update guide already refers to the change log. 
> 
> There are also some other changes (e.g. Redis becoming a hard 
> dependency) that could be documented more explicitly. 
> 
> 
> [0] https://github.com/ckan/ckan/blob/master/CHANGELOG.rst 
> 
> 
> Regards, 
> Florian
> 
> 
> "ckan-dev" <ckan-dev-bounces at lists.okfn.org> schrieb am 04.09.2017 
20:16:00:
> 
> > Von: dporto <dporto at gmail.com> 
> > An: CKAN Development Discussions <ckan-dev at lists.okfn.org>, 
> > Datum: 04.09.2017 20:30 
> > Betreff: [ckan-dev] New config properties and upgrade version 
> > Gesendet von: "ckan-dev" <ckan-dev-bounces at lists.okfn.org> 
> > 
> > I've recently migrate from 2.6.2 to 2.7.0 following the steps defined 
at
> > [1] http://docs.ckan.org/en/ckan-2.7.0/maintaining/upgrading/
> > upgrade-source.html
> > 
> > I've noticed that custom ini file remains the same (as it is expected)
> > But I've seen that now exists new key/value properties that don't
> > appear in my files
> > 
> > e.g. redis-url
> > http://docs.ckan.org/en/ckan-2.7.0/maintaining/
> > configuration.html#ckan-redis-url
> > 
> > I wonder if it should be documented in previoud upgrading guide [1] ?
> > 
> > David
> > _______________________________________________
> > ckan-dev mailing list
> > ckan-dev at lists.okfn.org
> > https://lists.okfn.org/mailman/listinfo/ckan-dev
> > Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
> 
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev

> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20170905/ebb591b6/attachment-0003.html>


More information about the ckan-dev mailing list