You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and is synced regularily to Crowdin. Once a translation has reached
96
+
and is synced regularly to Crowdin. Once a translation has reached
96
97
A SATISFACTORY PERCENTAGE it will be synced back into this repo and
97
98
included in the next released version.
98
99
@@ -256,6 +257,19 @@ in production, please download the latest release tag version. All the
256
257
branches will be protected via GitHub, all the PRs to every branch must
257
258
be reviewed by two maintainers and must pass the automatic tests.
258
259
260
+
## Releasing Gitea
261
+
262
+
* Let $vmaj, $vmin and $vpat be Major, Minor and Patch version numbers, $vpat should be rc1, rc2, 0, 1, ...... $vmaj.$vmin will be kept the same as milestones on github or gitea in future.
263
+
* Before releasing, confirm all the version's milestone issues or PRs has been resolved. Then discuss the release on discord channel #maintainers and get agreed with almost all the owners and mergers. Or you can declare the version and if nobody against in about serval hours.
264
+
* If this is a big version first you have to create PR for changelog on branch `master` with PRs with label `changelog` and after it has been merged do following steps:
265
+
* Create `-dev` tag as `git tag -s -F release.notes v$vmaj.$vmin.0-dev` and push the tag as `git push origin v$vmaj.$vmin.0-dev`.
266
+
* When CI has finished building tag then you have to create a new branch named `release/v$vmaj.$vmin`
267
+
* If it is bugfix version create PR for changelog on branch `release/v$vmaj.$vmin` and wait till it is reviewed and merged.
268
+
* Add a tag as `git tag -s -F release.notes v$vmaj.$vmin.$`, release.notes file could be a temporary file to only include the changelog this version which you added to `CHANGELOG.md`.
269
+
* And then push the tag as `git push origin v$vmaj.$vmin.$`. Drone CI will automatically created a release and upload all the compiled binary. (But currently it didn't add the release notes automatically. Maybe we should fix that.)
270
+
* If needed send PR for changelog on branch `master`.
271
+
* Send PR to [blog repository](https://github.com/go-gitea/blog) announcing the release.
272
+
259
273
## Copyright
260
274
261
275
Code that you contribute should use the standard copyright header:
0 commit comments