diff --git a/RELEASES.md b/RELEASES.md
index 6ca1048ec..34a3a73a6 100644
--- a/RELEASES.md
+++ b/RELEASES.md
@@ -16,13 +16,13 @@ Patch releases are based on the major/minor release branch, the release cadency
 ### Minor Release Support Matrix
 | Version | Supported          |
 | ------- | ------------------ |
-| Harbor v1.8.x   | :white_check_mark: |
-| Harbor v1.9.x   | :white_check_mark: |
+| Harbor v2.1.x   | :white_check_mark: |
+| Harbor v2.0.x   | :white_check_mark: |
 | Harbor v1.10.x   | :white_check_mark: |
 
 ### Upgrade path and support policy
 The upgrade path for Harbor is (1) 1.0.x patch releases are always compatible with its major and minor version. For example, previous released 1.8.x can be upgraded to most recent 1.8.4 release. (2) Harbor only supports two previous minor releases to upgrade to current minor release. For example, 1.9.0 will only support 1.7.0 and 1.8.0 to upgrade from, 1.6.0 to 1.9.0 is not supported. One should upgrade to 1.8.0 first, then to 1.9.0.
-The Harbor project maintains release branches for the three most recent minor releases, each minor release will be maintained for approximately 9 months. There is no mandated timeline for major versions and there are currently no criteria for shipping a new major version (i.e. Harbor 2.0.0).
+The Harbor project maintains release branches for the three most recent minor releases, each minor release will be maintained for approximately 9 months.
 
 ### Next Release
 The activity for next release will be tracked in the [up-to-date project board](https://github.com/orgs/goharbor/projects/1). If your issue is not present in the corresponding release, please reach out to the maintainers to add the issue to the project board.