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 1 commit
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 @@ -87,6 +87,7 @@ That includes:
> - 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.
> - For a GA, we need to mark the version we are releasing as "Stable" and the next one as "Development".
> - Update [Install Operator](https://vitess.io/docs/get-started/operator/#install-the-operator): the snippet where we clone the vitess repository has to include `git checkout release-xx.0`. With `xx` being the major version we are releasing.
- **Create a new GitHub Milestone**
> - Our GitHub Milestones is a good representation of all our ongoing development cycles. We have a Milestone for `main` and for all release branches.
> - After doing Code Freeze, we can create a new GitHub Milestone that matches the next development cycle.
Expand Down
Loading