mirror of
https://github.com/go-gitea/gitea
synced 2024-09-11 00:47:00 +02:00
Add HOWTO for releasing Gitea (#5054)
* Add HOWTO for releasing Gitea Used instructions from: https://github.com/go-gitea/gitea/pull/2609#issuecomment-352159155 * Update CONTRIBUTING.md
This commit is contained in:
parent
f44d066876
commit
1ecf92ade2
@ -16,6 +16,7 @@
|
|||||||
- [Maintainers](#maintainers)
|
- [Maintainers](#maintainers)
|
||||||
- [Owners](#owners)
|
- [Owners](#owners)
|
||||||
- [Versions](#versions)
|
- [Versions](#versions)
|
||||||
|
- [Releasing Gitea](#releasing-gitea)
|
||||||
- [Copyright](#copyright)
|
- [Copyright](#copyright)
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
@ -256,6 +257,17 @@ in production, please download the latest release tag version. All the
|
|||||||
branches will be protected via GitHub, all the PRs to every branch must
|
branches will be protected via GitHub, all the PRs to every branch must
|
||||||
be reviewed by two maintainers and must pass the automatic tests.
|
be reviewed by two maintainers and must pass the automatic tests.
|
||||||
|
|
||||||
|
## Releasing Gitea
|
||||||
|
|
||||||
|
* 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.
|
||||||
|
* 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.
|
||||||
|
* If this is a big version, then you have to create a new branch named `release/v$vmaj.$vmin`
|
||||||
|
* Create PR for changelog on branch `release/v$vmaj.$vmin`
|
||||||
|
* After your PR reviewed and merged, and CI passed, add a tag as `git tag -s -F release.notes v$vmaj.$vmin.$`, release.notes file could be a temporory file to only include the changelog this version which you added to `CHANGELOG.md`.
|
||||||
|
* 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.)
|
||||||
|
* Send PR for changelog on branch `master`.
|
||||||
|
* Send PR to [blog repository](https://github.com/go-gitea/blog) announcing the release.
|
||||||
|
|
||||||
## Copyright
|
## Copyright
|
||||||
|
|
||||||
Code that you contribute should use the standard copyright header:
|
Code that you contribute should use the standard copyright header:
|
||||||
|
Loading…
Reference in New Issue
Block a user