[RELEASE] v0.4.2 hotfix

[iameskild]

Release Checklist

Release details

Scheduled release date - 2022/06/08

Release captain responsible - @iameskild

Starting point - a new release is out

• Create this issue to track and discuss the upcoming release.
• Use the previous release issue for any final release-specific discussions, then close.
  • This can be a good time to debrief and discuss improvements to the release process.

Looking forward - planning

• Create milestone for next release (if it doesn't already exist) and link it back here.
• Triage bugs to determine what be should included in the release and add it to the milestone.
• What new features, if any, will be included in the release and add it to the milestone.
  • This will be, in large part, determined by the roadmap.
  • Is there a focus for this release (i.e. UX/UI, stabilitation, etc.)?

Pre-release process

• Decide on a date for the release.
  • What outstanding issues need to be addressed?
  • Has documentation been updated appropriately?
  • Are there any breaking changes that should be highlighted?
  • Are there any upstream releases we are waiting on?
  • Do we need to update the dask versions in the qhub-dask?
  • Will there be an accompanying blog post?
• Prepare for the release.
  • Announce build freeze.
  • Release Candidate (RC) cycle.
    • Perform end-to-end testing.
      • For minor releases, relying on the end-to-end integration tests might suffice.
    • Cut RC via GHA release workflow (w/ "This is a pre-release" checked).
    • End-user validation.
      • If possible, pull in volunteers to help test.
      • (Repeat steps if necessary)
  • Update RELEASE.md notes.

Cut the official release

• Tag, build and push docker images
• Update and cut release for qhub-dask meta package on Conda-Forge.
• Cut Test PyPI release via manual workflow_dispatch.
• Cut PyPI release via GHA release workflow.
  • Copy release notes from RELEASE.md.
• Merge automated release PR for qhub on Conda-Forge.

[iameskild]

We are also currently unable to deploy on AWS for another unrelated reason. This was confirmed when we ran the AWS integration tests with v0.4.2rc1 and it failed as described in @tylerpotts' #1302, see logs here.

Given the minimal change and sever impact of leaving it unresolved, @viniciusdc and I decided it made sense to include Tyler's fix in this release as well.

[iameskild]

RC2 was released and passed all the integration tests. It should now be ready for the official release.

[iameskild]

Update to checklist might include:

• Define hotfix (cherry-picking) workflow

Update to the process:

• Update Publish CI to include PyPI test publish first (no separate workflow)