github.com/argoproj/argo-cd/v3@v3.2.1/docs/developer-guide/release-process-and-cadence.md (about)

     1  # Release Process And Cadence
     2  
     3  ## Release Cycle
     4  
     5  ### Schedule
     6  
     7  These are the upcoming releases dates:
     8  
     9  | Release | Release Candidate 1   | General Availability | Release Champion                                        | Release Approver                                      | Checklist                                                     |
    10  |---------|-----------------------|----------------------|---------------------------------------------------------|-------------------------------------------------------|---------------------------------------------------------------|
    11  | v2.6    | Monday, Dec. 19, 2022 | Monday, Feb. 6, 2023 | [William Tam](https://github.com/wtam2018)              | [William Tam](https://github.com/wtam2018)            | [checklist](https://github.com/argoproj/argo-cd/issues/11563) |
    12  | v2.7    | Monday, Mar. 20, 2023 | Monday, May 1, 2023  | [Pavel Kostohrys](https://github.com/pasha-codefresh)   | [Pavel Kostohrys](https://github.com/pasha-codefresh) | [checklist](https://github.com/argoproj/argo-cd/issues/12762) |
    13  | v2.8    | Monday, Jun. 26, 2023 | Monday, Aug. 7, 2023 | [Keith Chong](https://github.com/keithchong)            | [Keith Chong](https://github.com/keithchong)          | [checklist](https://github.com/argoproj/argo-cd/issues/13742) |
    14  | v2.9    | Monday, Sep. 18, 2023 | Monday, Nov. 6, 2023 | [Leonardo Almeida](https://github.com/leoluz)           | [Leonardo Almeida](https://github.com/leoluz)         | [checklist](https://github.com/argoproj/argo-cd/issues/14078) |
    15  | v2.10   | Monday, Dec. 18, 2023 | Monday, Feb. 5, 2024 | [Katie Lamkin](https://github.com/kmlamkin9)            |                                                       | [checklist](https://github.com/argoproj/argo-cd/issues/16339) |
    16  | v2.11   | Friday, Apr. 5,  2024 | Monday, May 6, 2024  | [Pavel Kostohrys](https://github.com/pasha-codefresh)   | [Pavel Kostohrys](https://github.com/pasha-codefresh) | [checklist](https://github.com/argoproj/argo-cd/issues/17726) |
    17  | v2.12   | Monday, Jun. 17, 2024 | Monday, Aug. 5, 2024 | [Ishita Sequeira](https://github.com/ishitasequeira)    | [Pavel Kostohrys](https://github.com/pasha-codefresh) | [checklist](https://github.com/argoproj/argo-cd/issues/19063) |
    18  | v2.13   | Monday, Sep. 16, 2024 | Monday, Nov. 4, 2024 | [Regina Voloshin](https://github.com/reggie-k)          | [Pavel Kostohrys](https://github.com/pasha-codefresh) | [checklist](https://github.com/argoproj/argo-cd/issues/19513) |
    19  | v2.14   | Monday, Dec. 16, 2024 | Monday, Feb. 3, 2025 | [Ryan Umstead](https://github.com/rumstead)             | [Pavel Kostohrys](https://github.com/pasha-codefresh) | [checklist](https://github.com/argoproj/argo-cd/issues/20869) |
    20  | v3.0    | Monday, Mar. 17, 2025 | Tuesday, May 6, 2025 | [Regina Voloshin](https://github.com/reggie-k)          |                                                       | [checklist](https://github.com/argoproj/argo-cd/issues/21735) |
    21  | v3.1    | Monday, Jun. 16, 2025 | Monday, Aug. 4, 2025 | [Christian Hernandez](https://github.com/christianh814) | [Alexandre Gaudreault](https://github.com/agaudreault) | [checklist](#) |
    22  | v3.2    | Monday, Sep. 15, 2025 | Monday, Nov. 3, 2025 | [Nitish Kumar](https://github.com/nitishfy)             |                                                       | [checklist](#) |
    23  | v3.3    | Monday, Dec. 15, 2025 | Monday, Feb. 2, 2026 |                                                         |                                                       |
    24  
    25  Actual release dates might differ from the plan by a few days.
    26  
    27  ### Release Process
    28  
    29  #### Minor Releases (e.g. 2.x.0)
    30  
    31  A minor Argo CD release occurs four times a year, once every three months. Each General Availability (GA) release is
    32  preceded by several Release Candidates (RCs). The first RC is released seven weeks before the scheduled GA date. This
    33  effectively means that there is a seven-week feature freeze.
    34  
    35  These are the approximate release dates:
    36  
    37  * The first Monday of February
    38  * The first Monday of May
    39  * The first Monday of August
    40  * The first Monday of November
    41  
    42  Dates may be shifted slightly to accommodate holidays. Those shifts should be minimal.
    43  
    44  #### Patch Releases (e.g. 2.5.x)
    45  
    46  Argo CD patch releases occur on an as-needed basis. Only the three most recent minor versions are eligible for patch
    47  releases. Versions older than the three most recent minor versions are considered EOL and will not receive bug fixes or
    48  security updates.
    49  
    50  #### Release Champion
    51  
    52  To help manage all the steps involved in a release, we will have a Release Champion. The Release Champion will be
    53  responsible for a checklist of items for their release. The checklist is an issue template in the Argo CD repository.
    54  
    55  The Release Champion can be anyone in the Argo CD community. Some tasks (like cherry-picking bug fixes and cutting
    56  releases) require [Approver](https://github.com/argoproj/argoproj/blob/master/community/membership.md#community-membership)
    57  membership. The Release Champion can delegate tasks when necessary and will be responsible for coordinating with the
    58  Approver.
    59  
    60  ### Feature Acceptance Criteria
    61  
    62  To be eligible for inclusion in a minor release, a new feature must meet the following criteria before the release’s RC
    63  date.
    64  
    65  If it is a large feature that involves significant design decisions, that feature must be described in a Proposal, and
    66  that Proposal must be reviewed and merged.
    67  
    68  The feature PR must include:
    69  
    70  * Tests (passing)
    71  * Documentation
    72  * If necessary, a note in the Upgrading docs for the planned minor release
    73  * The PR must be reviewed, approved, and merged by an Approver.
    74  
    75  If these criteria are not met by the RC date, the feature will be ineligible for inclusion in the RC series or GA for
    76  that minor release. It will have to wait for the next minor release.
    77  
    78  ### Security Patch Policy
    79  
    80  CVEs in Argo CD code will be patched for all supported versions. Read more about supported versions in the [security policy for Argo CD](https://github.com/argoproj/argo-cd/security/policy#supported-versions).
    81  
    82  ### Dependencies Lifecycle Policy
    83  
    84  Dependencies are evaluated before being introduced to ensure they:
    85  
    86  1) are actively maintained
    87  2) are maintained by trustworthy maintainers
    88  
    89  These evaluations vary from dependency to dependencies.
    90  
    91  Dependencies are also scheduled for removal if the project has been deprecated or if the project is no longer maintained.
    92  
    93  CVEs in dependencies will be patched for all supported versions if the CVE is applicable and is assessed by Snyk to be
    94  of high or critical severity. Automation generates a [new Snyk scan weekly](../snyk/index.md).