mirror of
https://github.com/rpm-software-management/tito.git
synced 2025-02-24 04:32:46 +00:00
25 lines
956 B
Markdown
25 lines
956 B
Markdown
|
# Maintenance documentation
|
||
|
|
|
||
|
|
## Release process
|
||
|
|
|
||
|
|
If you are releasing a new version of Tito, please follow these steps:
|
||
|
|
|
||
|
|
1. Make sure Travis tests are passing
|
||
|
|
2. Make sure it is possible to build tito package from `master` branch for all
|
||
|
|
currently supported Fedora versions. Either by using [mock][mock], or using
|
||
|
|
Copr `tito release copr --test`
|
||
|
|
3. Make sure that `[fedora]` releaser in `.tito/releasers.conf` contains all
|
||
|
|
currently supported Fedora and Epel branches.
|
||
|
|
4. Tag a new version `tito tag` and follow its instructions
|
||
|
|
5. Go to the [GitHub releases page][releases] and
|
||
|
|
- write a propper release notes
|
||
|
|
- upload source tarball that you generate with `tito build --tgz`
|
||
|
|
6. Push new version into Fedora DistGit and build it in Koji
|
||
|
|
`tito release fedora`
|
||
|
|
7. Make sure those builds succeeds and submit updates into Bodhi
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
[mock]: https://github.com/rpm-software-management/mock
|
||
|
|
[releases]: https://github.com/dgoodwin/tito/releases
|