mirror of
https://github.com/rpm-software-management/tito.git
synced 2025-02-24 04:32:46 +00:00
Describe how to release tito
This commit is contained in:
parent
3e06357df7
commit
57287ec902
2 changed files with 26 additions and 3 deletions
|
@ -32,7 +32,6 @@ git_url = git://example.com
|
||||||
releaser = tito.release.FedoraGitReleaser
|
releaser = tito.release.FedoraGitReleaser
|
||||||
branches = master el6 epel7 epel8 f30 f31 f32
|
branches = master el6 epel7 epel8 f30 f31 f32
|
||||||
|
|
||||||
[copr-dgoodwin]
|
[copr]
|
||||||
releaser = tito.release.CoprReleaser
|
releaser = tito.release.CoprReleaser
|
||||||
project_name = tito
|
project_name = @rpm-software-management/tito
|
||||||
|
|
||||||
|
|
24
doc/maintenance.md
Normal file
24
doc/maintenance.md
Normal file
|
@ -0,0 +1,24 @@
|
||||||
|
# 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
|
Loading…
Add table
Reference in a new issue