Andres Vazquez
Andres Vazquez
I proposed at Django the change you suggested @gslaboch: https://github.com/django/django/pull/11819
This is [done in catalog-next](https://github.com/GSA/catalog.data.gov/blob/master/requirements/pyproject.toml#L20:L20) and probably should be closed
Should we close this @roll ?
Postgis [was removed](https://github.com/okfn/docker-ckan/commit/abb04686c983b5d824caea0be64f55d2028ad4fb#diff-e445ac9993610b3a85a685ffd5ceb890L2). I agree, it's a good idea to add a easy way to add this when required.
Starting check for `ckanext-archiver` [here](https://github.com/ckan/ckanext-archiver/pull/83)
Starting check for `ckanext-fluent` [here](https://github.com/ckan/ckanext-fluent/pull/41)
Starting check `ckanext-hierarchy` [here](https://github.com/ckan/ckanext-hierarchy/pull/49)
Starting check `ckanext-dcat` [here](https://github.com/ckan/ckanext-dcat/pull/208) The workflow to run the test is awaiting approval from a maintainer
We need to add `ckanext-report` considering it's a requirement for other extensions CKAN 2.10 Support for `ckanext-report` started [here](https://github.com/ckan/ckanext-report/pull/27/files)
Starts with `ckanext-qa` [here](https://github.com/ckan/ckanext-qa/pull/73) CKAN 2.9 + python 3 update never happened