debian-forge/RELEASE.md
Christian Kellner 6a31747aa6 RELEASE.md: update to mention 'v' tag prefix
The rule for the tag name is to have a 'v' prefix, update the
release instruction to reflect that. Also remove the Packit
header, because we don't use Packit at all anymore.
2020-03-05 12:39:46 +01:00

23 lines
654 B
Markdown

# How to create new release
Use the `bump-version` target to bump the version:
```
$ make bump-version
```
Check that the spec file is correctly modified.
Create new commit from this change; this commit will become the new tag.
The name of the tag should the be the new version number prefixed by `v`.
```
$ git tag -a v<version-number> -m <some description>
$ git push origin <version-number>
```
Create new release on Github containing the number of this release as its
name, the same number as a tag, and description copied from the previous
one.
Once the Github release is available, follow the standard procedure for
creating a Fedora update.