diff options
| author | Antoine GIRARD <sapk@users.noreply.github.com> | 2017-08-25 15:13:54 +0200 |
|---|---|---|
| committer | Kim "BKC" Carlbäcker <kim.carlbacker@gmail.com> | 2017-08-28 19:08:24 +0200 |
| commit | 019c90ab8f2ee1cf6b43d6a0c759e322b9859271 (patch) | |
| tree | db733c7ed97ee5067c3b604ad244644c1ae23db2 /CONTRIBUTING.md | |
| parent | edb95faba2534d9bf53068b69db99ffa7b71938f (diff) | |
| download | gitea-019c90ab8f2ee1cf6b43d6a0c759e322b9859271.tar.gz gitea-019c90ab8f2ee1cf6b43d6a0c759e322b9859271.zip | |
Update CONTRIBUTING following #2329 discussion
Creation of release branch before end of release dev and releases candidates + follow semver semantic (minor, patch)
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3ddabcbe30..7a6871680e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -97,7 +97,7 @@ Please use your real name, we really dislike pseudonyms or anonymous contributio ## Release Cycle -We adopted a release schedule to streamline the process of working on, finishing, and issuing releases. The overall goal is to make a major release every two months, which breaks down into one month of general development followed by one month of testing and polishing known as the release freeze. A release is maintained by issuing minor releases to only correct critical problems such as crashes or security issues. All the feature pull requests should be merged in the first month of one release period. +We adopted a release schedule to streamline the process of working on, finishing, and issuing releases. The overall goal is to make a minor release every two months, which breaks down into one month of general development followed by one month of testing and polishing known as the release freeze. All the feature pull requests should be merged in the first month of one release period and during the frozen period a corresponding release branch is open for fix backported from master. Release candidate are made along this period for user testing to obtain a final version that is maintained in this branch. A release is maintained by issuing patch releases to only correct critical problems such as crashes or security issues. The current release cycle is aligned to start on December 25 to February 24, next is February 25 to April 24, and etc. On this cycle, we also maybe publish the previous release minor version. For example, the current release version is v1.1, but we maybe also publish v1.0.2. When we publish v1.2, then we will stop publish v1.0.3. |