Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion site/content/en/contributions/DEVELOP.md
Original file line number Diff line number Diff line change
Expand Up @@ -199,7 +199,7 @@ Here are some brief benchmark reports about Envoy Gateway:
- It will take up nearly 550MiB memory and 11s total CPU time for (1 GatewayClass + 1 Gateway + 500 HTTRoutes) settings


[Quickstart]: https://github.com/envoyproxy/gateway/blob/main/docs/latest/user/quickstart.md
[Quickstart]: https://gateway.envoyproxy.io/docs/tasks/quickstart/
[make]: https://www.gnu.org/software/make/
[Github Actions]: https://docs.github.com/en/actions
[workflows]: https://github.com/envoyproxy/gateway/tree/main/.github/workflows
Expand Down
8 changes: 4 additions & 4 deletions site/content/en/contributions/RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ export GITHUB_REMOTE=origin
13. Ensure your release branch is up-to-date and tag the head of your release branch with the release candidate number.

```shell
git tag -a v${MAJOR_VERSION}.${MINOR_VERSION}.0-rc.${RELEASE_CANDIDATE_NUMBER} -m 'Envoy Gateway v${MAJOR_VERSION}.${MINOR_VERSION}.0-rc.${RELEASE_CANDIDATE_NUMBER} Release Candidate'
git tag -a v${MAJOR_VERSION}.${MINOR_VERSION}.0-rc.${RELEASE_CANDIDATE_NUMBER} -m "Envoy Gateway v${MAJOR_VERSION}.${MINOR_VERSION}.0-rc.${RELEASE_CANDIDATE_NUMBER} Release Candidate"
```

14. Push the tag to the Envoy Gateway repository.
Expand Down Expand Up @@ -214,7 +214,7 @@ export GITHUB_REMOTE=origin
8. Tag the head of your release branch with the release tag. For example:

```shell
git tag -a v${MAJOR_VERSION}.${MINOR_VERSION}.0 -m 'Envoy Gateway v${MAJOR_VERSION}.${MINOR_VERSION}.0 Release'
git tag -a v${MAJOR_VERSION}.${MINOR_VERSION}.0 -m "Envoy Gateway v${MAJOR_VERSION}.${MINOR_VERSION}.0 Release"
```

__Note:__ The tag version differs from the release branch by including the `.0` patch version.
Expand Down Expand Up @@ -363,7 +363,7 @@ export GITHUB_REMOTE=origin
9. Tag the head of your release branch with the release tag. For example:

```shell
git tag -a v${MAJOR_VERSION}.${MINOR_VERSION}.${PATCH_VERSION} -m 'Envoy Gateway v${MAJOR_VERSION}.${MINOR_VERSION}.${PATCH_VERSION} Release'
git tag -a v${MAJOR_VERSION}.${MINOR_VERSION}.${PATCH_VERSION} -m "Envoy Gateway v${MAJOR_VERSION}.${MINOR_VERSION}.${PATCH_VERSION} Release"
```

10. Push the tag to the Envoy Gateway repository.
Expand Down Expand Up @@ -412,7 +412,7 @@ It's important that the world knows about the release. Use the following steps t

[release notes]: https://github.com/envoyproxy/gateway/tree/main/release-notes
[Pull Request]: https://github.com/envoyproxy/gateway/pulls
[Quickstart]: https://github.com/envoyproxy/gateway/blob/main/docs/user/quickstart.md
[Quickstart]: https://gateway.envoyproxy.io/docs/tasks/quickstart/
[Build and Test]: https://github.com/envoyproxy/gateway/blob/main/.github/workflows/build_and_test.yaml
[release GitHub action]: https://github.com/envoyproxy/gateway/blob/main/.github/workflows/release.yaml
[release workflow]: https://github.com/envoyproxy/gateway/actions/workflows/release.yaml
Expand Down