From 57287ec9025be148a49bc59dd04f46b7a7b24321 Mon Sep 17 00:00:00 2001 From: Jakub Kadlcik Date: Thu, 26 Mar 2020 18:24:52 +0100 Subject: [PATCH] Describe how to release tito --- .tito/releasers.conf | 5 ++--- doc/maintenance.md | 24 ++++++++++++++++++++++++ 2 files changed, 26 insertions(+), 3 deletions(-) create mode 100644 doc/maintenance.md diff --git a/.tito/releasers.conf b/.tito/releasers.conf index da81700..e19de26 100644 --- a/.tito/releasers.conf +++ b/.tito/releasers.conf @@ -32,7 +32,6 @@ git_url = git://example.com releaser = tito.release.FedoraGitReleaser branches = master el6 epel7 epel8 f30 f31 f32 -[copr-dgoodwin] +[copr] releaser = tito.release.CoprReleaser -project_name = tito - +project_name = @rpm-software-management/tito diff --git a/doc/maintenance.md b/doc/maintenance.md new file mode 100644 index 0000000..f819710 --- /dev/null +++ b/doc/maintenance.md @@ -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