mirror of
https://github.com/gogs/gogs.git
synced 2026-05-06 17:38:00 +02:00
Updated Release Cycle (markdown)
@@ -8,7 +8,7 @@ The main purpose of this document is to design a pattern to make every minor rel
|
||||
|
||||
## Release
|
||||
|
||||
The first release candidate of a minor version is on **Third Tuesday of Every Month**, the `develop` branch will be merged to `master` branch. After the first RC is published, bug fixes will be all going to branch `release/{major.minor}`, e.g. `release/0.10`. Then the cycle goes into two directions:
|
||||
The first release candidate of a minor version is on **Third Tuesday of Every Month**, the `develop` branch will be merged to `master` branch. After the first RC is published, the cycle goes into two directions:
|
||||
|
||||
1. If there is no critical bug fix for on-going minor release, official release will be published on **next Tuesday**.
|
||||
2. If there are critical bug fixes for on-going minor release, next version of RC (RC -> RC2, RC2 -> RC3) will be published instead on **next Tuesday**.
|
||||
|
||||
Reference in New Issue
Block a user