search

stackabletech / issues

This repository is only for issues that concern multiple repositories or don't fit into any specific repository
2 stars 0 forks source link

chore(tracking): Release SDP 24.11 #647

Open NickLarsenNZ opened 1 month ago

NickLarsenNZ commented 1 month ago

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: https://github.com/stackabletech/issues/issues/649)
  • 🟠 2024-11-15 - Target release date (could be earlier)

~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
- [x] Find out what is left before updating operator-rs across repos
- [ ] https://github.com/stackabletech/operator-rs/issues/898
- [ ] https://github.com/stackabletech/operator-templating/issues/450
- [ ] https://github.com/stackabletech/issues/issues/652
- [ ] https://github.com/stackabletech/docker-images/issues/831

[!TIP] These tasks should be done a week or so before the release date.

### Pre-release
- [ ] https://github.com/stackabletech/operator-templating/pull/457
- [x] [Run all of the test suites in Jenkins (with all product versions, not just "nightly")](https://github.com/stackabletech/issues/issues/647#issuecomment-2443567223)
- [ ] https://github.com/stackabletech/issues/issues/657
- [ ] https://github.com/stackabletech/issues/issues/658
- [ ] https://github.com/stackabletech/issues/issues/664
- [x] 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
- [ ] https://github.com/stackabletech/demos/issues/62#issuecomment-2382221177
- [x] https://github.com/stackabletech/demos/pull/119
- [ ] https://github.com/stackabletech/issues/issues/649
- [ ] https://github.com/stackabletech/crddocs/issues/44
- [ ] https://github.com/stackabletech/demos/pull/122
- [ ] https://github.com/stackabletech/stackable-utils/issues/84
- [ ] https://github.com/stackabletech/stackable-utils/issues/83
- [ ] https://github.com/stackabletech/issues/issues/611
- [ ] https://github.com/stackabletech/crddocs-generator/pull/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
- [x] Temporarily remove branch protection before pushing the release branches/tags
- [x] Create release branches for docker-images (see stackable-utils for script to create branches)
- [x] Create release tag(s) for docker-images (see stackable-utils for scripts to create tags)
- [x] Create release branches for operators (see stackable-utils for script to create branches)
- [x] Create release tag(s) for operators (see stackable-utils for scripts to create tags)
- [x] Create release branch for demos (see stackable-utils for scripts to create branch)
- [x] ~~Create release tag for stackable-cockpit (optional, highly experimental, requires manual tag creation)~~
- [x] Update release version in changelogs on main branches (see stackable-utils for script to do this)
- [x] [Merge changelog PRs for operators](https://github.com/search?q=org%3Astackabletech+Update+CHANGELOG.md+from+release+24.11.0&type=pullrequests&p=2) @NickLarsenNZ
- [ ] https://github.com/stackabletech/crddocs/pull/45
- [ ] Check (selected) integration tests on the new release branches @NickLarsenNZ
- [ ] https://github.com/stackabletech/issues/issues/672
- [ ] https://github.com/stackabletech/demos/pull/116
- [x] Run/Check demos with dev release and main branch and create draft PR for release-related changes
- [ ] https://github.com/stackabletech/stackable-cockpit/pull/334
- [x] Test `stackablectl` with locally updated (to new release number) `releases.yaml` @Techassi
- [ ] https://github.com/stackabletech/release/pull/33
- [ ] ARM testing @Maleware
- [x] 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
#### 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**
- [ ] https://github.com/stackabletech/documentation/pull/679
- [ ] 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
- [ ] Cut a release branch (see [scripts/make-release-branch.sh](https://github.com/stackabletech/documentation/blob/main/scripts/make-release-branch.sh))
- [ ] Update releases in the playbook (see [scripts/publish-new-version.sh](https://github.com/stackabletech/documentation/blob/main/scripts/publish-new-version.sh))
- [ ] Update version of main documentation repo (antora.yml on the release branch)
- [ ] Update SDP release version in documentation/modules/ROOT/pages/getting-started.adoc
- [ ] Set the release to "Released" in the Feature Tracker and create a new release
- [ ] 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
- [ ] 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)

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](https://github.com/stackabletech/community/discussions/categories/announcements) 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, 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
- [ ] Update the list of supported SDP releases in Jira (ping Jim)
- [ ] Bump Rust version. This can be done [in this file](https://github.com/stackabletech/operator-templating/blob/main/config/rust.yaml) by changing `rust_version` and also for the ubi base image [here](https://github.com/stackabletech/docker-images/blob/main/ubi8-rust-builder/Dockerfile#L25). Please be aware that this action will change it for all repositories at the same time (when merging the templating PRs).
- [ ] Check/bump versions of kube-rs and k8s-openapi (also checking the version of k8s we build against)
- [ ] Check/bump ubi9 base image
- [ ] preflight now checks automatically it's own version and only runs if latest ~~Check/bump preflight~~
- [ ] Openshift certification. Create an issue from this [template](https://github.com/stackabletech/issues/blob/main/.github/ISSUE_TEMPLATE/olm_manifests.md) for the OLM manifests
- [ ] Define product versions to include in the next release
- [ ] Add branch protection to release branches once they are stable
- [ ] Mark any end-of-life releases as such [in the documentation](https://github.com/stackabletech/documentation/blob/f751e7ff7cddacae7d2c6c2c6c1d1c877c7aa11c/antora.yml#L18)
- [ ] https://github.com/stackabletech/issues/issues/669
NickLarsenNZ commented 3 weeks ago

Tests are all passing All green

soenkeliebau commented 1 week ago

AirFlow

New version: 2.10.x https://airflow.apache.org/docs/apache-airflow/stable/release_notes.html#airflow-2-10-0-2024-08-15

Kafka

New version: 3.8.x https://archive.apache.org/dist/kafka/3.8.0/RELEASE_NOTES.html

Superset

Only bugfix version

Trino

New version: 455 ( includes 454, 453, 452)

ZooKeeper

Only bugfix version

Druid

New version: 30 (was experimental before) https://druid.apache.org/docs/30.0.0/release-info/release-notes

HBase

New version: 2.6.x (was experimental before, so not actually new)

Hadoop

New version 3.4.x (was experimental before, so not actually new)

NiFi

New version 2.0.x (was experimental before, so not actually new)

Hive

Spark

Only bugfix version