Stackable Release 24.11.1

Release checklists

Replace the items in the task lists below with the applicable Pull Requests / Issues

General Pre-Requisites (before Feature Freeze)

Early Pre-release tasks

• Release Retro 24.11.1 #684
• Define product versions to include in the next release Patch release
• Update and release operator-rs workspace members
• Update Rust toolchain of operators
• Update Rust dependencies of operators
• Update Container Images

Pre-release

• Run all of the test suites in Jenkins (with all product versions, not just "nightly")
• Check and update getting-started scripts
• Check and update demo charts
• Test demos and upgrade from stable to nightly release
• Ensure integration tests are successful on OpenShift
• Check stackable-utils scripts in dry-run mode work
• release: 24.11.1 airflow-operator#567
• release: 24.11.1 commons-operator#317
• release: 24.11.1 druid-operator#675
• release: 24.11.1 hbase-operator#610
• release: 24.11.1 hdfs-operator#638
• release: 24.11.1 hello-world-operator#150
• release: 24.11.1 hive-operator#558
• release: 24.11.1 kafka-operator#808
• release: 24.11.1 listener-operator#266
• release: 24.11.1 nifi-operator#735
• release: 24.11.1 opa-operator#674
• release: 24.11.1 secret-operator#540
• release: 24.11.1 spark-k8s-operator#513
• release: 24.11.1 superset-operator#584
• release: 24.11.1 trino-operator#691
• release: 24.11.1 zookeeper-operator#903
• release: 24.11.1 docker-images#973

Other Pre-Requisites (before Feature Freeze)

Search for open issues labeleded with scheduled-for/24.11.1

Other release-specific pre-requisites

• Choose a viable release candidate: 24.11.1-rc2
• Check that all PRs (e.g. with labels scheduled-for/xx.yy.z) have been merged
• Discuss where the patch release notes go (probably a new section above the 24.11 release?)

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

• Run the stackable-utils release scripts for promoting 24.11.1-rc2 to 24.11.1 @adwk67
• chore: Add release 24.11.1 crddocs#46
• Deploy CRD docs website for the new release triggering the deploy action
• Test stackablectl with locally updated (to new release number) releases.yaml @Techassi
• chore: Update 24.11 release to use 24.11.1 images release#35
• chore(tracking): Check and update getting-started scripts for SDP Release 24.11.1 #688
• chore: Release stackablectl-24.11.2 stackablectl#346
• fix: Update references for 24.11.1 demos#138
• chore(tracking): Test demos for 24.11.1 demos#137
• Check that an upgrade can be performed on an existing cluster without data loss (cycling demo) @NickLarsenNZ
• Run all integration tests for x86_64 @NickLarsenNZ
• Run all integration tests for aarch64 Deferring until integrations tests are moved to Github Actions
• OpenShift testing (discuss internally) - will be done as part of the OS certification

Documentation tasks

• Create a stackabletech/documentation branch called docs/release-notes-24.11.1
• refactor: Restructure docs into partials and handle patch releases documentation#703
• chore(tracking): Release Notes for SDP 24.11.1 documentation#704
• Add the 24.11.1 section titles to changelogs in the main branch @adwk67
• Cherry-pick the updated release notes into the release branch
• Update SDP release version in main stackabletech/documentation/modules/ROOT/pages/getting-started.adoc and test the release install command
• Cherry-pick the updated SDP release version commit from main into the release branch
• Update releases in the playbook (see scripts/publish-new-version.sh)
• Update antora.yaml version in stackabletech/demos on the release branch - the stackable-utils release-scripts should do this like they do for products and operators.
• Set the release to "Released" in the Feature Tracker and create a new release (how?)

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)
• Write a description of new demos for homepage/demos section
• Announce Release on LinkedIn
• Announce Release in Newsletter (optional)
• Produce a release highlight video (optional)
• Announce Release on Hacker News (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)
• Post an announcement via OSBA (Ping Lars, [email protected])
• Send announcement to Kubernetes Podcast (Ping Lars)
• Send announcement to Heiser
• 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. Tracking
• Mark any releases older than one year as "end-of-life" in the documentation
• Post 24.11.1 release retro (use issue created at the start of the process)
• chore(tracking): SDP Release 25.3.0 #686
• feat: Release candidates stackable-utils#95