Change the release cycle to match actual situations #16430
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## main #16430 +/- ##
==========================================
+ Coverage 44.24% 45.42% +1.18%
==========================================
Files 695 717 +22
Lines 82341 84162 +1821
==========================================
+ Hits 36429 38230 +1801
+ Misses 40014 39784 -230
- Partials 5898 6148 +250
Continue to review full report at Codecov.
|
techknowlogick
merged commit efeb8e8
into
go-gitea:main
1 of 2 checks passed
1 of 2 checks passed
approvals/lgtm
this commit looks good
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
It seems we never obey a release cycle of two months. According the history release cycle, I think 3 or 4 months for one release is suitable.