Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modify the release instructions to properly clone Vitess when using the vtop examples #14889

Merged
merged 4 commits into from
Jan 4, 2024
Merged

Modify the release instructions to properly clone Vitess when using the vtop examples #14889

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
19ebfd1
Modify the release instructions to properly clone Vitess when using t…
frouioui Jan 4, 2024
793b47b
Remove whitespaces
frouioui Jan 4, 2024
e6d74d7
Update the release instructions with how to update the entire get sta…
frouioui Jan 4, 2024
d1acad0
Review suggestion
frouioui Jan 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions doc/internal/release/how-to-release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,7 @@ That includes:
> - There are several pages we want to update:
> - [The releases page](https://vitess.io/docs/releases/): we must add the new release to the list with all its information and link. The links can be broken (404 error) while we are preparing for the release, this is fine.
> - [The local install page](https://vitess.io/docs/get-started/local/): we must use the proper version increment for this guide and the proper SHA. The SHA will have to be modified once the Release Pull Request and the release is tagged is merged.
> - [The Vitess Operator for Kubernetes page](https://vitess.io/docs/get-started/operator/#install-the-operator), [the Local Install via source for Mac page](https://vitess.io/docs/get-started/local-mac/#install-vitess), [the Local Install via Docker page](https://vitess.io/docs/get-started/local-docker/#check-out-the-vitessiovitess-repository), and [the Vttestserver Docker Image page](https://vitess.io/docs/18.0/get-started/vttestserver-docker-image/#check-out-the-vitessiovitess-repository): we must checkout to the proper release branch after cloning Vitess.
frouioui marked this conversation as resolved.
Show resolved Hide resolved
> - If we are doing a GA or RC release follow the instructions below:
> - There are two scripts in the website repository in `./tools/{ga|rc}_release.sh`, use them to update the website documentation. The scripts automate:
> - For an RC, we need to create a new entry in the sidebar which represents the next version on `main` and mark the version we are releasing as RC.
Expand Down
Loading