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
In the catalog-app we are using a fork of the ckanext-qa extension (on the datagov branch). We are not sure about which repo should be consider upstream.
When there's a new release upstream, we can get onto it in under an hour
When there's a new release upstream, we see a notification in a Slack channel
If the upstream maintainers don't already use versioning, there's an issue in their tracker requesting they do.
If the upstream maintainers don't already have tests, there's an issue in their tracker requesting they add them.
We have tests for this extension running in CI (upstream have no tests or CI)
Tasks
Create a test environment with the catalog-app
Ask upstream for tests and CI
Test (by now) manually this extension in this environment.
Measure the effort to move the catalog-app to this upstream version.
Upstream do not use tags for versions, do not have a change log file and version is 0.1 from the begining (6 years ago). Ask upstream for improve versioning.
If we consider this extension as an important one, do a deep analysis on forks to check for bug fixes or improvements.
Connect our Slack channel with new release news in upstream
Analysis & notes
DavidRead version starts this repo (we consider this repo upstream by now). Last update: Mar 22, 2017
GSA version last update: March 9, 2016
Other repos continue working on it until today. They just work to upgrade to py3 and add translation capabilities
Our fork is Ahead in 36 commits and Behind 49 commits but these versions have not diverged a lot. This potential PR show us the changes between our datagov branch and upstream. The changes do not seem significant. It should not require much effort updating to this version.
It's a good idea to define an environment with the catalog-app and just change ckanext-report to the official version and run tests.
Recommendation
Define the upstream version and move to it
The text was updated successfully, but these errors were encountered:
Description
In the catalog-app we are using a fork of the ckanext-qa extension (on the datagov branch). We are not sure about which repo should be consider upstream.
As a part of a plan to upgrade CKAN extensions in use, and in order to improve the way that we manage forks we need to upgrade this extension.
Acceptance Criteria
Tasks
Analysis & notes
DavidRead version starts this repo (we consider this repo upstream by now). Last update: Mar 22, 2017
GSA version last update: March 9, 2016
Other repos continue working on it until today. They just work to upgrade to py3 and add translation capabilities
Our fork is Ahead in 36 commits and Behind 49 commits but these versions have not diverged a lot. This potential PR show us the changes between our
datagov
branch and upstream. The changes do not seem significant. It should not require much effort updating to this version.It's a good idea to define an environment with the catalog-app and just change ckanext-report to the official version and run tests.
Recommendation
Define the upstream version and move to it
The text was updated successfully, but these errors were encountered: