mirror of
https://github.com/go-gitea/gitea.git
synced 2024-11-27 05:11:54 +08:00
Improving CONTRIBUTING.md for backport details (#23057)
See the changes. Two key points: * Necessary enhancements could be backported. * The backports shouldn't break downgrade between minor releases.
This commit is contained in:
parent
4d2d3bd65d
commit
33e556e67a
@ -299,9 +299,7 @@ known as the release freeze. All the feature pull requests should be
|
|||||||
merged before feature freeze. And, during the frozen period, a corresponding
|
merged before feature freeze. And, during the frozen period, a corresponding
|
||||||
release branch is open for fixes backported from main branch. Release candidates
|
release branch is open for fixes backported from main branch. Release candidates
|
||||||
are made during this period for user testing to
|
are made during this period for user testing to
|
||||||
obtain a final version that is maintained in this branch. A release is
|
obtain a final version that is maintained in this branch.
|
||||||
maintained by issuing patch releases to only correct critical problems
|
|
||||||
such as crashes or security issues.
|
|
||||||
|
|
||||||
Major release cycles are seasonal. They always begin on the 25th and end on
|
Major release cycles are seasonal. They always begin on the 25th and end on
|
||||||
the 24th (i.e., the 25th of December to March 24th).
|
the 24th (i.e., the 25th of December to March 24th).
|
||||||
@ -311,6 +309,16 @@ for the previous version. For example, if the latest, published release is
|
|||||||
v1.2, then minor changes for the previous release—e.g., v1.1.0 -> v1.1.1—are
|
v1.2, then minor changes for the previous release—e.g., v1.1.0 -> v1.1.1—are
|
||||||
still possible.
|
still possible.
|
||||||
|
|
||||||
|
The previous release gets fixes for:
|
||||||
|
|
||||||
|
- Security issues
|
||||||
|
- Critical bugs
|
||||||
|
- Regressions
|
||||||
|
- Build issues
|
||||||
|
- Necessary enhancements (including necessary UI/UX fixes)
|
||||||
|
|
||||||
|
The backported fixes should avoid breaking downgrade between minor releases as much as possible.
|
||||||
|
|
||||||
## Maintainers
|
## Maintainers
|
||||||
|
|
||||||
To make sure every PR is checked, we have [team
|
To make sure every PR is checked, we have [team
|
||||||
|
Loading…
Reference in New Issue
Block a user