1
0
mirror of https://github.com/qTox/qTox.git synced 2024-03-22 14:00:36 +08:00

docs(MAINTAINING): update instructions for release version bump

This commit is contained in:
Zetok Zalbavar 2017-05-13 13:25:54 +01:00
parent 2f05ff0947
commit 1d71952dc5
No known key found for this signature in database
GPG Key ID: C953D3880212068A

View File

@ -184,8 +184,12 @@ Follow steps for adding translations from Weblate up to step 5. Next:
- `PATCH` bump when there have been only fixes added. If changes include - `PATCH` bump when there have been only fixes added. If changes include
something more than just bugfixes, bump `MAJOR` or `MINOR` version something more than just bugfixes, bump `MAJOR` or `MINOR` version
accordingly. accordingly.
- update version for windows/osx packages using [`./tools/update-versions.sh`] - bumping a higher-level version "resets" lower-version numbers, e.g.
script `v1.7.1 → v2.0.0`
- update version:
- bump version number in `cmake/Installation.cmake`
- for windows/osx packages use the [`./tools/update-versions.sh`] script,
e.g. `./tools/update-versions.sh 1.11.0`
- before creating a `MAJOR`/`MINOR` release generate changelog with `clog`. - before creating a `MAJOR`/`MINOR` release generate changelog with `clog`.
- in a `MAJOR`/`MINOR` release tag should include information that changelog - in a `MAJOR`/`MINOR` release tag should include information that changelog
is located in the `CHANGELOG.md` file, e.g. `For details see CHANGELOG.md` is located in the `CHANGELOG.md` file, e.g. `For details see CHANGELOG.md`
@ -196,8 +200,6 @@ Follow steps for adding translations from Weblate up to step 5. Next:
- when making a `PATCH` tag, include in tag message short summary of what the - when making a `PATCH` tag, include in tag message short summary of what the
tag release fixes, and to whom it's interesting (often only some tag release fixes, and to whom it's interesting (often only some
OSes/distributions would find given `PATCH` release interesting). OSes/distributions would find given `PATCH` release interesting).
- bumping a higher-level version "resets" lower-version numbers, e.g.
`v1.7.1 → v2.0.0`
- create and GPG-sign tarball using [`./tools/create-tarball.sh`] script, and - create and GPG-sign tarball using [`./tools/create-tarball.sh`] script, and
upload the tarball to a github release. upload the tarball to a github release.