release-bot
release-bot copied to clipboard
Release to Github and PyPI with ease.
See also https://github.com/user-cont/release-bot/pull/140#pullrequestreview-201724268
For example in https://github.com/packit-service/ogr/issues/15 @lachmanfrantisek was ignored because ``` WARNING Author association 'CONTRIBUTOR' not in ['MEMBER', 'OWNER', 'COLLABORATOR'] ``` even he was in part of 'The packit team' whose members...
- https://pypi.org/project/zest.releaser - https://github.com/zestsoftware/zest.releaser - https://zestreleaser.readthedocs.io - https://opensourcehacker.com/2012/08/14/high-quality-automated-package-releases-for-python-with-zest-releaser - https://techblog.socialwifi.com/how-to-painlessly-release-open-source-python-package
Top-level logic is present in the `run()` method. We should have an e2e test which validates this logic.
Right now the bot does the whole pipeline every time. There is a suggestion from @bowlofeggs and @pypingou to be able to do the whole run, but only some part....
We have a pretty good testing infrastructure right now: * We have unit tests * We have integration tests. * They cover the complete functionality (PyPI, Fedora, Github, PR creation)....
There could be a use case, when user might want to do something right after release, like trigger a docker hub build, or send an email to somewhere. TBD: -...
So we've encoutered an issue when some projects don't name their releases by just version number, but with a ['v' prefix](https://github.com/openshift/source-to-image/releases) or [something else](https://github.com/fedora-modularity/meta-test-family/releases). I don't think there's a need...