-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Labels
Description
Stackable Release 24.11
Important
Important dates:
- 🟢 2024-08-06 - Release planning
- 🟢 2024-09-11 - Lock product versions
- 🟢 2024-10-23 - Final operator-rs release (excluding bug fixes before the release)
- 🟢 2024-10-25 - Bump operator-rs in each operator
- 🟢 2024-10-28 - Begin pre-release tasks (week before on-site)
- 🟢 2024-11-08 - Bump jmx_exporter, or roll back (See: JMX Exporter Fix #649)
- 🟢 2027-11-15 - Official release date
See the 24.11 feature tracking project This link now points to a future release.
Release checklists
Replace the items in the task lists below with the applicable Pull Requests / Issues
General Prerequisites (before Feature Freeze)
Tip
These tasks should be done earlier in the process to lessen the burden at Pre-release time.
Early Pre-release tasks
- Find out what is left before updating operator-rs across repos
- chore: Update and release workspace members for SDP 24.11 operator-rs#898
- chore: Pre-release Rust toolchain and pre-commit updates operator-templating#450
- chore(tracking): Update Rust dependencies of operators for SDP 24.11 #652
- chore: Update Container Images for Stackable Release 24.11 docker-images#831
Tip
These tasks should be done a week or so before the release date.
Pre-release
- chore(template): Niv updates operator-templating#457
- Run all of the test suites in Jenkins (with all product versions, not just "nightly")
- chore(tracking): Check and update getting-started scripts for 24.11 #657
- chore(tracking): Test demos on nightly versions for 24.11 #658
- chore(tracking): Ensure integration tests are successful on OpenShift for 24.11 #664
- Check stackable-utils scripts in dry-run mode work
Other Pre-Requisites (before Feature Freeze)
Search for open issues labeleded with scheduled-for/2024-11
Other release-specific pre-requisites
- Fix the data-lakehouse-iceberg-trino-spark demo demos#62 (comment)
- chore: Bump Helm charts demos#119
- JMX Exporter Fix #649
- Broken link crddocs#44
- fix: Use dev release for stacks demos#122
- Handle updates for demos stackable-utils#84
- Extend post-release script to update docker-images Changelog stackable-utils#83
- Template getting_started with
makeinstead of adding instructions to the comments #611 - fix: Adjust Go version in go.mod file crddocs-generator#25
Feature freeze
This will not be so crucial with release branches, but is nonetheless sensible as it will make it easier to cherry-pick any release-related bugfixes from main into the release branch.
End of the release cycle (Release day)
Technical tasks
- Temporarily remove branch protection before pushing the release branches/tags
- Create release branches for docker-images (see stackable-utils for script to create branches)
- Create release tag(s) for docker-images (see stackable-utils for scripts to create tags)
- Create release branches for operators (see stackable-utils for script to create branches)
- Create release tag(s) for operators (see stackable-utils for scripts to create tags)
- Create release branch for demos (see stackable-utils for scripts to create branch)
-
Create release tag for stackable-cockpit (optional, highly experimental, requires manual tag creation) - Update release version in changelogs on main branches (see stackable-utils for script to do this)
- Merge changelog PRs for operators @NickLarsenNZ
- chore: Add release 24.11.0 crddocs#45
- Check (selected) integration tests on the new release branches @NickLarsenNZ
- chore(tracking): Check and update getting-started scripts for 24.11 #672
- feat: Update demos for Release 24.11 demos#116
- Run/Check demos with dev release and main branch and create draft PR for release-related changes
- chore: Release stackablectl-24.11.0 stackable-cockpit#334
- Test
stackablectlwith locally updated (to new release number)releases.yaml@Techassi - chore: Add 24.11 release release#33
- ARM testing @Maleware
- Check that an upgrade can be performed on an existing cluster without data loss. (cycling-data)
- Run all of the test suites @NickLarsenNZ
- OpenShift Testing @razvan
- Fixes accidentally deleted serviceaccount and rolebinding objects operator-rs#909
- fix!: Correctly construct OIDC endpoints operator-rs#910
Documentation tasks
- Check the Changelog and/or issue labels to compile Release Highlights Add to draft PR below
- Compile list of new product versions that are supported and compile a list of new product features to include in the Release Highlights Add to draft PR below
- Upgrade guide: Document how to use stackablectl to uninstall all and install new release
- Upgrade guide: Document how to use helm to uninstall all and install new release
- Upgrade guide: Every breaking change of all our operators
- Upgrade guide: List dropped supported product versions (if there are some)
- Upgrade guide: List dropped supported operators (if there are some)
- Upgrade guide: List supported k8s versions
- Add 24.11 Release Notes documentation#679
- Update SDP release version in documentation/modules/ROOT/pages/getting-started.adoc
- Update the getting-started page in the main docs and check it works with this release: https://github.com/stackabletech/documentation/blob/main/modules/ROOT/pages/getting-started.adoc
- docs(getting-started): Update version references documentation#685
- docs(getting-started): Update version references documentation#686
- chore: Change docs version from nightly to 24.11 demos#134
- Cut a release branch (see scripts/make-release-branch.sh)
- Update releases in the playbook (see scripts/publish-new-version.sh)
- chore(docs): Remove superfluous page-aliases demos#135
- chore: Add release branches to the playbooks for release 24.11 documentation#684
- Update version of main demos repo (antora.yml on the release branch) - manually done by @Techassi - needs scripting
- Set the release to "Released" in the Feature Tracker and create a new release
- If not already done, check the demos work for the new release
-
OpenShift 4.16 certification (update the release notes on main and cherry pick to the release branch)defering to SDP 24.11.1
Marketing tasks can now reference published documentation.
Marketing tasks
- Write marketing / customer oriented release summary to be published in the marketing channels
- Update the homepage banner (as long as we have it) to point to the new release
- Write a blogpost / news article announcing the new release (optional)
- Announce Release on LinkedIn
- Announce Release in Newsletter (optional)
- Post an announcement in the GitHub Discussions Announcement forum and make it a pinned discussion while at the same time removing the old pinned thread
- Post an announcement in Discord
- Post an announcement on DOK Community in the #be-shameless Channel (Ping Lars or Jim)
- Send announcement to Heise
- Ping the stackable-ionos-tech channel or anyone responsible once all tags are created
Post-release tasks
- Update the list of supported SDP releases in Jira (ping Jim)
-
Openshift certification. Create an issue from this template for the OLM manifestsDeferring to 24.11.1 - Update antora.yml to mark 23.7 as EoL documentation#672
- Release Retro 24.11.0 #669
- Release templates updates post 24.11.0 #680
- Create a release-notes PR template to be used by the release tracking ticket documentation#693
- Create the next release tracking task chore(tracking): SDP Release 24.11.1 #683
- Fix the e2e security demo (fix(stack/end-to-end-security): Skip DB restore if the DB exists demos#139 and fix(stack/end-to-end-security): Skip DB restore if the DB exists demos#140)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Done