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.

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

docs: Clarify the approach to release candidates #11934

Merged
merged 7 commits into from
Nov 23, 2023
Merged
Show file tree
Hide file tree
Changes from 1 commit
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
Next Next commit
docs: define the approach to release candidates
Signed-off-by: Tim Collins <[email protected]>
  • Loading branch information
tico24 committed Nov 22, 2023
commit 2ab0c8f8c52377b30bedd49f4fbc0b00fd719196
1 change: 1 addition & 0 deletions .spelling
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,7 @@ PVCs
Peixuan
Ploomber
Postgres
RCs
Roadmap
RoleBinding
s3
Expand Down
7 changes: 5 additions & 2 deletions docs/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,11 @@ Both the `argo-server` and `argocli` should be the same version as the controlle

## 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.
tico24 marked this conversation as resolved.
Show resolved Hide resolved

Release candidates (RCs) for each major release are typically available for 4-6 weeks before the release becomes generally available (GA). Features may be shipped in subsequent release candidates.
tico24 marked this conversation as resolved.
Show resolved Hide resolved

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 release timeline, and a new release candidate will be cut for testing before pushing to GA.
tico24 marked this conversation as resolved.
Show resolved Hide resolved

Otherwise, we typically release every two weeks:

Expand Down