Update release procedures #1871

tnozicka · 2024-03-28T13:13:33Z

Description of your changes:
The PR brings up our release procedure to up to date with our recent infra changes and with how we've done it for v1.12.

The new procedure also no longer requires blocking master branch.

tnozicka · 2024-04-03T08:30:46Z

#1028 (comment)
/retest

tnozicka · 2024-04-16T07:21:54Z

/assign zimnx

zimnx · 2024-04-17T08:26:27Z

release.md

-    git push upstream upstream/master:refs/heads/vX.Y
-    ```
+### Mark `master` as the next release
+Moving `master` to the next release is done by creating a new `vX.Y+1.Z-alpha.0` tag for the next version. It can be either just the `git` tag or a proper `alpha` release, but given the very little difference the `beta` of the previous release, it's usability is limited to worth the effort.


Procedure should explain what we do, not leave the decision for someone who executes it. We either do alpha tags or not.

Suggested change

Moving `master` to the next release is done by creating a new `vX.Y+1.Z-alpha.0` tag for the next version. It can be either just the `git` tag or a proper `alpha` release, but given the very little difference the `beta` of the previous release, it's usability is limited to worth the effort.

Moving `master` to the next release is done by creating a new `vX.Y+1.Z-alpha.0` tag for the next version.

zimnx · 2024-04-17T08:27:49Z

release.md

 1. Enable building docs from `vX.Y` branch by adding an entry to `docs/source/conf.py`.
   ```
-   BRANCHES = ['master', 'v0.3', 'v1.0', 'v1.1', 'vX.Y']
+   BRANCHES = ['master', 'v1.11', 'v1.12', 'vX.Y']


Suggested change

BRANCHES = ['master', 'v1.11', 'v1.12', 'vX.Y']

BRANCHES = ['master', 'vX.Y-2', 'vX.Y-1', 'vX.Y']

zimnx · 2024-04-17T08:30:29Z

release.md

+
+#### From a pre-release
+```
+skopeo copy --all docker://quay.io/scylladb/scylla-operator:X.Y.0-rc.I docker://quay.io/scylladb/scylla-operator:X.Y.0


Suggested change

skopeo copy --all docker://quay.io/scylladb/scylla-operator:X.Y.0-rc.I docker://quay.io/scylladb/scylla-operator:X.Y.0

skopeo copy --all docker://quay.io/scylladb/scylla-operator:X.Y.Z-rc.I docker://quay.io/scylladb/scylla-operator:X.Y.Z

zimnx · 2024-04-17T08:30:44Z

release.md

+skopeo copy --all docker://quay.io/scylladb/scylla-operator:X.Y.0-rc.I docker://quay.io/scylladb/scylla-operator:X.Y.0
+```
+```
+skopeo copy --all docker://quay.io/scylladb/scylla-operator:X.Y.0 docker://docker.io/scylladb/scylla-operator:X.Y.0


Suggested change

skopeo copy --all docker://quay.io/scylladb/scylla-operator:X.Y.0 docker://docker.io/scylladb/scylla-operator:X.Y.0

skopeo copy --all docker://quay.io/scylladb/scylla-operator:X.Y.Z docker://docker.io/scylladb/scylla-operator:X.Y.Z

zimnx · 2024-04-17T08:33:12Z

release.md


-1. Submit a PR using `master` as target branch.
+### ScyllaDB User Slack
+Send a post to the `#scylla-operator` channel in ScyllaDB-Users Slack based on the following template.


IMO we should include notable changes paragraph as well, to promote what is important.

seems already included in the forum link - I've extended the description

zimnx · 2024-04-17T08:34:21Z

release.md

-   - `#scylla-operator` channel in ScyllaDB-Users Slack
-   - users mailing list (https://groups.google.com/g/scylladb-users)
+### Beta
+`beta` is a testing release that comes from a release branch.


It doesn't explain when it's tagged.

zimnx · 2024-06-04T10:42:42Z

release.md

+Moving `master` to the next release is done by creating a new `vX.Y+1.Z-alpha.0` tag for the next version. It can be either just the `git` tag or a proper `alpha` release, but given the very little difference the `beta` of the previous release, it's usability is limited to worth the effort.
+```
+git fetch [email protected]:scylladb/scylla-operator.git
+git tag -s -a vX.Y+1.Z-alpha.0 "${revision}" -m "vX.Y+1.Z-alpha.0"


${revision} is undefined

scylla-operator-bot · 2024-07-02T07:44:30Z

@tnozicka: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gke-release-script-latest	`c1cef98`	link	true	`/test e2e-gke-release-script-latest`

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

zimnx

/lgtm

scylla-operator-bot · 2024-07-02T08:41:08Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tnozicka, zimnx

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

~~OWNERS~~ [tnozicka,zimnx]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

tnozicka · 2024-07-02T10:09:46Z

#1996 (comment)

this is docs only
/override ci/prow/e2e-gke-parallel-clusterip

scylla-operator-bot · 2024-07-02T10:09:50Z

@tnozicka: Overrode contexts on behalf of tnozicka: ci/prow/e2e-gke-parallel-clusterip

In response to this:

#1996 (comment)

this is docs only
/override ci/prow/e2e-gke-parallel-clusterip

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

tnozicka added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/documentation Categorizes issue or PR as related to documentation. labels Mar 28, 2024

scylla-operator-bot bot requested review from rzetelskik and zimnx March 28, 2024 13:13

scylla-operator-bot bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Mar 28, 2024

tnozicka force-pushed the update-release-instructions branch 2 times, most recently from b0b0d72 to c1cef98 Compare April 2, 2024 14:06

scylla-operator-bot bot assigned zimnx Apr 16, 2024

zimnx reviewed Apr 17, 2024

View reviewed changes

zimnx reviewed Jun 4, 2024

View reviewed changes

zimnx mentioned this pull request Jun 20, 2024

docs: Issue on page Scylla Operator Documentation #1981

Closed

Update release procedures

89e06a0

tnozicka force-pushed the update-release-instructions branch from c1cef98 to 89e06a0 Compare July 1, 2024 19:11

zimnx approved these changes Jul 2, 2024

View reviewed changes

scylla-operator-bot bot added the lgtm Indicates that a PR is ready to be merged. label Jul 2, 2024

scylla-operator-bot bot merged commit 6eb2c75 into scylladb:master Jul 2, 2024
12 checks passed

tnozicka deleted the update-release-instructions branch July 2, 2024 12:28

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update release procedures #1871

Update release procedures #1871

tnozicka commented Mar 28, 2024

tnozicka commented Apr 3, 2024

tnozicka commented Apr 16, 2024

zimnx Apr 17, 2024

tnozicka Jul 1, 2024

zimnx Apr 17, 2024

tnozicka Jul 1, 2024

zimnx Apr 17, 2024

tnozicka Jul 1, 2024

zimnx Apr 17, 2024

tnozicka Jul 1, 2024

zimnx Apr 17, 2024

tnozicka Jul 1, 2024

zimnx Apr 17, 2024

tnozicka Jul 1, 2024

zimnx Jun 4, 2024

tnozicka Jul 1, 2024

scylla-operator-bot bot commented Jul 2, 2024 •

edited

Loading

zimnx left a comment

scylla-operator-bot bot commented Jul 2, 2024

tnozicka commented Jul 2, 2024

scylla-operator-bot bot commented Jul 2, 2024

	Moving `master` to the next release is done by creating a new `vX.Y+1.Z-alpha.0` tag for the next version. It can be either just the `git` tag or a proper `alpha` release, but given the very little difference the `beta` of the previous release, it's usability is limited to worth the effort.
	Moving `master` to the next release is done by creating a new `vX.Y+1.Z-alpha.0` tag for the next version.

	BRANCHES = ['master', 'v1.11', 'v1.12', 'vX.Y']
	BRANCHES = ['master', 'vX.Y-2', 'vX.Y-1', 'vX.Y']

	skopeo copy --all docker://quay.io/scylladb/scylla-operator:X.Y.0-rc.I docker://quay.io/scylladb/scylla-operator:X.Y.0
	skopeo copy --all docker://quay.io/scylladb/scylla-operator:X.Y.Z-rc.I docker://quay.io/scylladb/scylla-operator:X.Y.Z

Update release procedures #1871

Update release procedures #1871

Conversation

tnozicka commented Mar 28, 2024

tnozicka commented Apr 3, 2024

tnozicka commented Apr 16, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

scylla-operator-bot bot commented Jul 2, 2024 • edited Loading

zimnx left a comment

Choose a reason for hiding this comment

scylla-operator-bot bot commented Jul 2, 2024

tnozicka commented Jul 2, 2024

scylla-operator-bot bot commented Jul 2, 2024

scylla-operator-bot bot commented Jul 2, 2024 •

edited

Loading