You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 5, 2023. It is now read-only.
As a data.gov developer, I want ckanext-spatial running with CKAN 2.9 and Python 3 so that we can move out of CKAN 2.8 and reduce our technical debt and meet compliance standards.
Acceptance Criteria
WHEN I view CI
THEN I see a successful job testing the extension under CKAN 2.9
AND I see a successful job testing the extension under CKAN 2.8
AND I see a successful job testing the extension under the legacy test environment
WHEN I remove the tests
THEN I see CI fail due to test coverage being below a threshold
User Story
As a data.gov developer, I want ckanext-spatial running with CKAN 2.9 and Python 3 so that we can move out of CKAN 2.8 and reduce our technical debt and meet compliance standards.
Acceptance Criteria
THEN I see a successful job testing the extension under CKAN 2.9
AND I see a successful job testing the extension under CKAN 2.8
AND I see a successful job testing the extension under the legacy test environment
THEN I see CI fail due to test coverage being below a threshold
Background
CKAN 2.9 extension tracker.
Details / tasks
ckanext-spatial has an existing branch to support Python 3 ckan/ckanext-spatial#249
Use the fork of ckanext-spatial for now and see how we can support merging of this PR.
The text was updated successfully, but these errors were encountered: