Merge pull request #1702 from shaneutt/shaneutt/v0.6.1-changelog

release v0.6.1

Author: k8s-ci-robot

CHANGELOG.md

@@ -2,6 +2,7 @@
 
 ## Table of Contents
 
+- [v0.6.1](#v061)
 - [v0.6.0](#v060)
 - [v0.6.0-rc2](#v060-rc2)
 - [v0.6.0-rc1](#v060-rc1)
@@ -21,6 +22,59 @@
 - [v0.1.0-rc2](#v010-rc2)
 - [v0.1.0-rc1](#v010-rc1)
 
+# v0.6.1
+
+This is a patch release that predominantly includes updated conformance tests
+for implementations to implement.
+
+For all major changes since the `v0.5.x` release series, please see the
+[v0.6.0](/#v060) release notes.
+
+## Bug Fixes
+
+- Our regex for validating path characters was updated to accurately identify
+  "p-chars" as per RFC-3986.
+  (#1644, @jackstine)
+- An erroneous "namespace" field was present in our webhook ClusterRoleBindings
+  and has been removed.
+  (#1684, @tao12345666333)
+
+## New Features
+
+- Conditions for Policies have been added to the Golang library, enabling
+  Go-based implementations to re-use those for their downstream Policies.
+  (#1682, @mmamczur)
+
+## Conformance Test Updates
+
+- Added conformance tests for checking Port, Scheme and Path to the extended and
+  experimental features.
+  (#1611, @LiorLieberman)
+- Added conformance tests for HTTP rewrite
+  (#1622, #1628, @LiorLieberman)
+- Added more conformance tests for path matching to catch known edge cases.
+  (#1627, @sunjayBhatia)
+- Added some initial conformance tests for TLSRoute passthrough.
+  (#1579, @candita)
+- Added conformance tests that exercise NotAllowedByListeners reason.
+  (#1669, @mlavacca)
+- Loosen the Accepted check in GatewayClass observed generation tests to
+  provide a more realistic test for implementations.
+  (#1655, @arkodg)
+- A "SkipTests" field has been added to accomodate implementations in
+  running subsets of the tests as needed, this can be particularly helpful
+  for new implementations that want to add conformance iteratively.
+  (#1578, @mlavacca)
+- Fixed a broken test for GRPCRoute that caused an erronous failure.
+  (#1692, @arkodg)
+- Added "all-features" flag to conformance test to enable all supported
+  features on test runs.
+  (#1642, @gyohuangxin)
+- Fixed usage of `net/http` default client in conformance test suite
+  (#1617, @howardjohn)
+- Fixed missing reference to NoMatchingParent in godoc
+  (#1671, @mlavacca)
+
 # v0.6.0
 
 ## Major Changes

RELEASE.md

@@ -37,17 +37,34 @@ release.
 
 The following steps must be done by one of the [Gateway API maintainers][gateway-api-team]:
 
+For a patch release:
+- Create a new branch in your fork named something like `<githubuser>/release-x.x.x`. Use the new branch
+  in the upcoming steps.
+- Use `git` to cherry-pick all relevant PRs into your branch.
+- Update `pkg/generator/main.go` with the new semver tag and any updates to the API review URL.
+- Run the following command `BASE_REF=vmajor.minor.patch make generate` which will update generated docs
+  and webhook with the correct version info. Note that the YAMLs will not work until the tag is actually
+  published in the next step.
+- Create a pull request of the `<githubuser>/release-x.x.x` branch into the `release-x.x` branch upstream
+  (which should already exist since this is a patch release).
+- Verify the CI tests pass and once the above merges publish a new Git tag. This can be done using the
+  `git` CLI or Github's [release][release] page.
+- Run the `make build-install-yaml` command which will generate
+  install files in the `release/` directory.
+- Attach these files to the Github release.
+- Update the `README.md` as needed for any latest release references.
+
 For a major or minor release:
 - Cut a `release-major.minor` branch that we can tag things in as needed.
 - Check out the `release-major.minor` release branch locally.
 - Update `pkg/generator/main.go` with the new semver tag and any updates to the API review URL.
 - Run the following command `BASE_REF=vmajor.minor.patch make generate` which will update generated docs
   and webhook with the correct version info. Note that the YAMLs will not work until the tag is actually
   published in the next step.
-- Publish a new Git tag. This can  be done using the `git` CLI or Github's [release][release]
-  page.
+- Verify the CI tests pass and once the above merges publish a new Git tag. This can be done using the
+  `git` CLI or Github's [release][release] page.
 - Run the `make build-install-yaml` command which will generate
-  install files in the `release/` directory
+  install files in the `release/` directory.
 - Attach these files to the Github release.
 - Update the `README.md` as needed for any latest release references.
 
@@ -62,7 +79,7 @@ For an RC release:
   This can  be done using the `git` CLI or Github's [release][release]
   page.
 - Run the `make build-install-yaml` command which will generate
-  install files in the `release/` directory
+  install files in the `release/` directory.
 - Attach these files to the Github release.
 
 [release]: https://github.com/kubernetes-sigs/gateway-api/releases