This feature is implemented in hotness, which is commenting in Bugzilla.
It's already implemented in dist-git and Pagure as well.
This is now waiting for new version of Pagure to be available in Fedora
infra,
dist-git with the changes is already available. :-)
You can look at the upcoming monitoring options in the-new-hotness
documentation [0].
Michal
[0] -
On 26. 01. 23 13:38, Jaroslav Skarvada wrote:
On Thu, Jan 26, 2023 at 1:09 PM Neal Gompa <ngompa13(a)gmail.com>
wrote:
> On Thu, Jan 26, 2023 at 7:02 AM Jaroslav Skarvada <jskarvad(a)redhat.com> wrote:
>> Hi,
>>
>> it seems Anitya correctly distinguishes stable and pre-release
>> releases but where to set that I want Fedora bugs only for the stable
>> releases? IIRC Pagure had a switch for it, but I am unable to find it
>> on the
https://src.fedoraproject.org/rpms/. There is only
>> "No-Monitoring", "Monitoring", and "Monitoring and
scratch builds". It
>> seems there is no information about it in the docs [1]
>>
> You configure it on
release-monitoring.org for the upstream project,
> not
src.fedoraproject.org.
Where? The
release-monitoring.org / Anitya correctly marks it as a
pre-release but the bug is still created. There is only a "Pre-release
filter" box, but I think it's a helper if the default regex doesn't
work, which in my case seems to work
Jaroslav
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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