chore(tracking): SDP Release 25.7.0 #722
Description
Important
Important dates:
- 2025-05-05 - Release planning
- 2025-06-02 - Lock product versions
- 2025-07-10 - Final operator-rs release
- 2025-07-10 - Begin bumping operator-rs crates in each operator
- 2025-07-18 - Begin release-branching tasks (might need to be pushed again)
- 2025-07-25 - Target release date (marketable)
Tip
Replace the items in the task lists below with the applicable Pull Requests / Issues.
Early Pre-release tasks
Tip
These tasks should be done earlier in the process to lessen the burden at Pre-release time.
- Create a "Release Retro" issue
- Define product versions to include in the next release
- chore: Bump product major/minor levels for Stackable Release 25.7.0 docker-images#1064
- chore: Bump product patch levels for Stackable Release 25.7.0 docker-images#1066
- Run
niv updateand test viamake run-dev(operator-templating)
Pre-release
Tip
These tasks should be done a week or so before the release date.
- chore: Update and release workspace members for Stackable Release 25.7.0 operator-rs#1018
- chore: Pre-release updates for Stackable Release 25.7.0 operator-templating#512
- chore(tracking): Update Rust dependencies of operators before SDP Release 25.7.0 #725
- Run all of the test suites in Jenkins. The following PRs fix discovered issues. A second run was successful.
- chore(tracking): Check and update getting-started scripts before SDP Release 25.7.0 #742
- chore(tracking): Update Helm charts for 25.7.0 demos#235
- chore(tracking): Test demo upgrades on nightly versions for 25.7.0 demos#236
- chore(tracking): Test demos on nightly versions for 25.7.0 demos#242
- Ensure integration tests are successful on OpenShift (run with
--test-suite openshiftagainst Replicated OKD) @NickLarsenNZ - Check stackable-utils scripts in dry-run mode work @NickLarsenNZ
- Search for open issues labeled with scheduled-for/25.7.0
- Search for open PRs labeled with scheduled-for/25.7.0
Release branching
Caution
A small change freeze is required until these tasks have been completed.
Tip
See stackable-utils for script to create tags and update changelogs.
- Create release branch for docker-images
- Create release branches for operators
- Create release branch for demos
- Wait for images to be built before proceeding
Release candidate testing
Tip
As issues are discovered, they can be fixed on the main branch, and cherry-picked into the release branch.
Please ensure the changelog is updated and correct for the release after cherry-picking changes.
Please also keep PR links as they are in main (do not update them for the cherry-picked PR).
Release tagging
Tip
See stackable-utils for script to create tags and update changelogs.
- Create release tag(s) for docker-images
- Create release tag(s) for operators
- Update release version in changelogs on main branches
- Wait for images to be built before proceeding
- Test
stackablectlwith locally updated (to new release number)releases.yaml@NickLarsenNZ - chore: Add 25.7.0 release release#38
-
Release stackablectlNo longer tied to the SDP release cycle
Release verification
Tip
These tasks do not block the Documentation tasks below and can be done concurrently.
- chore(tracking): Check and update getting-started scripts for SDP Release 25.7.0 #751
-
Test demos from scratch (25.7.0)We decided to only testhbase-hdfs-load-cycling-data, see below... - Check that an upgrade can be performed on an existing cluster without data loss (cycling demo) #752
- Run all integration tests (for both
x86_64andaarch64 - Ensure integration tests are successful on OpenShift (run with
--test-suite openshiftagainst Replicated OKD) @NickLarsenNZ See fix: Spark-connect test timing issues spark-k8s-operator#597
Documentation tasks
Tip
Name the release-notes branch docs/release-notes-25.7.0 so that the link below takes you directly to the Pull Request template.
- Add to the release notes that we plan on deprecating/removing Hive 3 in an upcoming release
- chore: Add 25.7.0 release crddocs#52
- Create a stackabletech/documentation branch called
docs/release-notes-25.7.0 - chore(tracking): Release Notes for SDP 25.7.0 documentation#757
- Update SDP release version in
documentation/modules/ROOT/pages/getting-started.adocand test the release install command - Cut a release branch (see scripts/make-release-branch.sh)
- Update releases in the playbook (see scripts/publish-new-version.sh)
- Remove any references to HEAD and main from the Antora playbooks on the release branch (replace with the release branch)
- 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 (ping @lfrancke)
- Update the getting-started page in the main docs and check it works with this release
Marketing tasks
Note
Marketing material can now reference published documentation.
- 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, mailto:info@osb-alliance.com)
- 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
- Upgrade and tests stacks that were skipped in chore(tracking): Test demos on nightly versions for 25.7.0 demos#242
- Test demo upgrades, which were skipped in the previous testing (optional)
- Update the list of supported SDP releases in Jira (ping @Jimvin)
- chore(tracking): OLM Manifests for SDP Release 25.7.0 #754
- Mark any releases older than one year as "end-of-life" in the documentation (update antora.yaml on the applicable branches).
- Release Retro 25.7.0 #723
- Update the release tracking templates (optional)
- Next release: chore(tracking): SDP Release 25.11.0 #759