From 4112606cdf02e30a38908e0e922f5bb7a9166922 Mon Sep 17 00:00:00 2001 From: terrytangyuan Date: Thu, 23 Nov 2023 07:40:28 +0000 Subject: [PATCH] deploy: fec39fad72ed22031fac305a208fd67fd011fa3b --- releases/index.html | 5 +- search/search_index.json | 2 +- sitemap.xml | 374 +++++++++++++++++++-------------------- sitemap.xml.gz | Bin 296 -> 296 bytes 4 files changed, 191 insertions(+), 190 deletions(-) diff --git a/releases/index.html b/releases/index.html index 1c724590a4e6..283254a8f84a 100644 --- a/releases/index.html +++ b/releases/index.html @@ -3952,8 +3952,9 @@

Supported VersionsSupported Version Skew

Both the argo-server and argocli should be the same version as the controller.

Release Cycle

-

New minor versions are released roughly every 6 months. Release candidates for each major release are typically available -for 4-6 weeks before the release becomes generally available.

+

New minor versions are released roughly every 6 months.

+

Release candidates (RCs) for major and minor releases are typically available for 4-6 weeks before the release becomes generally available (GA). Features may be shipped in subsequent release candidates.

+

When features are shipped in a new release candidate, the most recent release candidate will be available for at least 2 weeks to ensure it is tested sufficiently before it is pushed to GA. If bugs are found with a feature and are not resolved within the 2 week period, the features will be rolled back so as to be saved for the next major/minor release timeline, and a new release candidate will be cut for testing before pushing to GA.

Otherwise, we typically release every two weeks: