[RELEASE] `2023.10.1`

[iameskild]

Release Checklist

Release details

Scheduled release date - 2023/9/20

Release captain responsible - @iameskild

Starting point - a new release is out

• [x] Create this issue to track and discuss the upcoming release.
• [x] 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

• [x] Create milestone for next release (if it doesn't already exist) and link it back here.
• [x] Triage bugs to determine what be should included in the release and add it to the milestone.
• [x] 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, stabilization, etc.)?

Pre-release process

• [x] 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 nebari-dask?
  • Will there be an accompanying blog post?
• [x] Prepare for the release.
  • [x] Announce build freeze.
  • [x] Release Candidate (RC) cycle.
  • [x] Perform end-to-end testing. Use the Testing Checklist template.
    • For minor releases, relying on the end-to-end integration tests might suffice.
  • [x] Cut RC via GHA release workflow (w/ "This is a pre-release" checked).
  • [x] End-user validation.
    • If possible, pull in volunteers to help test.
    • (Repeat steps if necessary)
  • [x] Update RELEASE.md notes.

Cut the official release

These steps must be actioned in the order they appear in this checklist.

• [x] Tag, build and push docker images
• [x] Update and cut release for nebari-dask meta package on Conda-Forge.
• [x] Cut PyPI release via GHA release workflow.
  • Avoid appending v to tag.
  • Copy release notes from RELEASE.md.
• [x] Merge release branch into main
• [x] Merge automated release PR for nebari on Conda-Forge.

[iameskild]

RC1

[iameskild]

We're currently blocked by #1948 (issues related to recent conda-store releases). A question for the team is how much longer should we wait for those fixes?

cc @pavithraes @dharhas