volcano.sh/volcano@v1.9.0/docs/community/version-release.md (about)

     1  # Volcano Version Release
     2  
     3  ## Version Plan
     4  Version plan is usually put into practice **half month** before the latest version released. 
     5  #### Requirements Collection
     6  According to the feedback of community, we will collect requirements which are from **classical scenes** or **common 
     7  demands** in the last three months. All collected requirements will be listed in the requirements list, reviewed initially, 
     8  and prioritized.
     9  #### Community Review
    10  Requirement list will be submitted to the community weekly meeting for discussion. Community members will evaluate the 
    11  scenarios, rationality, feature design points, development workload and other dimensions of the requirements. After the 
    12  discussion, part of requirements will be settled as version features and published in the roadmap.
    13  
    14  ### Version Release
    15  Generally, we will release an official version such as 1.X every **three months**. Bug fix versions such as 1.X.X are 
    16  released any time we consider it necessary after some important bug fixed.
    17  #### Code Freeze
    18  In order to ensure the quality of master branch, repository will be frozen **two weeks** before official version released,
    19  during which only bug fix PRs are admitted to be merged. **Alpha** and **Beta** version also will be released in the period.
    20  #### Branch Checkout
    21  During the code frozen, a new branch whose name like `release-X.X.X` will be checkout to merge bug fix and published release.
    22  #### Release Publishment
    23   We will publish every release and related docker images. Users can find release in the release list and docker images in
    24   the DockerHub.
    25  #### Beta Test
    26  After every release published, some users and community members will be invited to join the Beta test. Any contributor is
    27  welcome to take part in the test. We will collect bug feedback and fix them immediately. Usually, this work will be going
    28  **one week** before official release published.
    29  #### Official Release Publishment
    30  After all the work above finished, official release will be published with note about feature introduction.