Can we figure out a creative way to do this in CI/CD?
If not, maybe we add a PR template to this repo that links to the steps for testing a new build on test.opendap.org, with a reminder to think about whether the changes being made require that manual test before merging.
Otherwise the build looks good and everything seems to pass, and we find out too late that we broke something. This has now happened twice in recent memory---first when we bumped a version number at the libdap4 level, and now again with the docker rewrite (#107).
Can we figure out a creative way to do this in CI/CD?
If not, maybe we add a PR template to this repo that links to the steps for testing a new build on test.opendap.org, with a reminder to think about whether the changes being made require that manual test before merging.
Otherwise the build looks good and everything seems to pass, and we find out too late that we broke something. This has now happened twice in recent memory---first when we bumped a version number at the libdap4 level, and now again with the docker rewrite (#107).