Update release.md

* remove preflight update (it is automatic now)
* move getting-started task before release
* a bit of cleanup

Author: razvan

.github/ISSUE_TEMPLATE/release.md

@@ -17,8 +17,9 @@ assignees: ''
 - [ ] Check Rust and e.g. cargo deps versions
 - [ ] Run/check getting-started scripts
 - [ ] Run/check demos with dev release and main branch and create draft PR for release-related changes
-- [ ] TestOLM packages on Openshift
+- [ ] Ensure integration tests are successful on OpenShift
 - [ ] Test SDP release upgrade against 2-3 demos (i.e. install release, run demo, bump release, check what needs to be patched)
+- [ ] TODO: get rid of this ? 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
 ```
 
 ```[tasklist]
@@ -39,7 +40,6 @@ This will not be so crucial with release branches, but is nonetheless sensible a
 - [ ] 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 tag for stackable-cockpit (optional, highly experimental, requires manual tag creation)
-- [ ] Ping the stackable-ionos-tech channel or anyone responsible once all tags are created
 - [ ] Update changelogs in main branches (see stackable-utils for script to do this)
 - [ ] Check (selected) integration tests (use a table in Nuclino - easier for concurrent editing)
 - [ ] Check getting started scripts (use a table in Nuclino)
@@ -60,18 +60,18 @@ This will not be so crucial with release branches, but is nonetheless sensible a
 - [ ] Upgrade guide: List supported k8s versions
 - [ ] Update version of main documentation repo
 - [ ] 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
 ```
 
 Marketing tasks can now reference published documentation.
 
 ```[tasklist]
 #### Marketing tasks
+- [ ] Ping the stackable-ionos-tech channel or anyone responsible once all tags are created
 - [ ] 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 hmepage/demos section
-- [ ] Announce Release on linkedIn
+- [ ] Announce Release on LinkedIn
 - [ ] Announce Release in Newsletter (optional)
 - [ ] Produce a release highlight video (optional)
 - [ ] Announce Release on Hacker News (optional)
@@ -85,12 +85,11 @@ Marketing tasks can now reference published documentation.
 
 ```[tasklist]
 ### Post-release tasks
-- [ ] Bump Rust version. This can be done [in this file](https://github.com/stackabletech/operator-templating/blob/main/repositories.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).
+- [ ] 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).
 - [ ] Run renovate manually by starting this action: https://github.com/stackabletech/ci/blob/main/.github/workflows/renovate.yml
 - [ ] Check/bump versions of kube-rs and k8s-openapi (also checking the version of k8s we build against)
 - [ ] Check/bump ubi8 base image
-- [ ] Check/bump preflight
-- [ ] Create issue for release-specific Openshift certification
+- [ ] Openshift certification
 - [ ] Define product versions to include in the next release
 - [ ] Add branch protection to release branches once they are stable
 ```