Closed gouttegd closed 1 year ago
How does this work now? do I switch to this branch and make a multiarch release as usual? What will happen to this branch afterwards?
Well, first, I need to sort out whatever happened here: https://github.com/INCATools/ontology-development-kit/actions/runs/5088547393/jobs/9145088129#step:6:9894
Looks like a Python package is (again) misbehaving, but what is weird is that no problem occurred when the tests ran against the master branch last night.
Once that is sorted and this PR is merged in BRANCH-1.4-MAINTENANCE
, then you can checkout that branch and start the build process as usual.
What will happen to that branch depends on whether we’ll need a 1.4.2 release (e.g. if another ROBOT version becomes available before we’re ready to publish ODK 1.5) or not: if we do, then whatever changes needed to make 1.4.2 will continue happening on that branch. If we don’t, then the branch dies off and we’ll start a BRANCH-1.5-MAINTENANCE
branch just after 1.5 is released.
OK, need to cherry-pick the fixes to the test suite that happened shortly after the 1.4 release, then it should be good.
All tests pass with the latest cherry picks, so merging to the 1.4-maintenance branch now.
Up to you to to start building the release. I’ll wait until the images are available on the Docker Hub before tagging the release here on GitHub.
This PR updates the 1.4.x maintenance branch to: