On Thu, Sep 26, 2019 at 09:08:16AM -0700, Adam Williamson wrote:
On Thu, 2019-09-26 at 15:46 +0000, Jeremy Cline wrote:
>
> Ah right, that makes a lot of sense.
>
> I can imagine automatically detecting the new upstream release, building
> that, and presenting the packager with a easy-to-review PR that you just
> click "merge" on instead of pointing the specfile at a new tarball.
This already basically happens, at least for things that are hooked up
to anitya:
https://bugzilla.redhat.com/show_bug.cgi?id=1751432
https://fedoraproject.org/wiki/Upstream_release_monitoring
You get a bug report with a patch attached, and it runs a scratch
build. This is great for simple release bumps, but there's still all
sorts of cases where it's not enough or you're just doing something
else.
I do have a little[0] experience with anitya, but it's not nearly as
hooked up as it could be and honestly Libraries.io generally does
better for tracking upstreams, it just lacks the mapping to downstreams.
Maybe we could add that and use it, or continue with anitya.
What I'd really like to see is a lot more "cleverness" from it regarding
versions and automatic backporting to various Fedora releases based on
semantic versioning. Also there's still manual steps you need to do as a
maintainer like downloading and then uploading the tarball.
[0]
https://github.com/release-monitoring/anitya/graphs/contributors