release-engineering/tito
1
0
Fork 0
mirror of https://github.com/rpm-software-management/tito.git synced 2025-02-23 04:02:46 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
tito/doc/maintenance.md
Jakub Kadlcik 2061732f6b Rename master branch to main 
Fix #438
2024-04-23 12:32:37 +02:00

1.2 KiB
Raw Permalink Blame History

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 main branch for all currently supported Fedora versions. Either by using 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 --use-version= (drop the .postX suffix) and follow its instructions
  5. Go to the GitHub releases page 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
  8. Release into PyPI with python3 setup.py sdist and twine upload dist/<NAME-VERSION>.tar.gz
  9. Manually bump tito.spec Version to <version>.post1 (in a separate commit) to make sure that the ENVRA from the main branch beats the one from distro.