On Wed, Dec 14, 2022 at 4:38 PM Ron Olson <tachokni...@gmail.com> wrote: > > Hey all- > > I’m curious how Upstream Monitoring works; I got a BZ filed that Swift 5.7.2 > is available, which I’m building now, but what surprised me was how fast the > new version was detected and brought to my attention. Does it use The New > Hotness? I set that up awhile ago but I don’t think it files BZ tickets (and > I must not have it set up correctly as it hasn’t notified me about any > releases for the past year). > > To be clear this isn’t a complaint, if anything it’s an awesome feature and > I’m just curious what the mechanism is that makes it work.
There's several components involved to make this work: - anitya, which powers release-monitoring.org: this is where you need to set up the project and set the Fedora package name for it, and which crawls projects for new versions regularly - the-new-hotness: the service which files bugs for new versions detected by anitya, if "Monitoring" is enabled for a package on src.fedoraproject.org I wonder why "(and I must not have it set up correctly as it hasn’t notified me about any releases for the past year)." happened, though. Fabio _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
