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.

Sign up for GitHub

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

Jump to bottom

docs: Clarify the approach to release candidates #11934

Merged
merged 7 commits into from
Nov 23, 2023
Merged

docs: Clarify the approach to release candidates #11934

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
2ab0c8f
docs: define the approach to release candidates
tico24 Oct 3, 2023
fa047cd
clarify based on feedback
tico24 Oct 3, 2023
71b379d
tweak wording
tico24 Nov 22, 2023
690c777
Merge branch 'master' into rc-docs
tico24 Nov 22, 2023
ab7d10c
This is a blank commit
tico24 Nov 22, 2023
941d3e6
Merge branch 'master' into rc-docs
tico24 Nov 22, 2023
26f67f6
This is a blank commit
tico24 Nov 23, 2023
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
Prev Previous commit
Next Next commit
clarify based on feedback 
Signed-off-by: Tim Collins <[email protected]>
  • Loading branch information
@tico24
tico24 committed Nov 22, 2023
commit fa047cd93ba182d7f46563a658a0fb35eaf07786
2 changes: 1 addition & 1 deletion docs/releases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Both the `argo-server` and `argocli` should be the same version as the controlle

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.
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 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

Expand Down