The information is not lost (it's already emitted by Anitya in anitya.project.version.update.v2 message topic), The New Hotness just don't know how to work with it yet. It's planned as an upcoming feature.

Michal

On 09. 12. 21 16:54, Michael Catanzaro wrote:
On Thu, Dec 9 2021 at 03:59:39 PM +0100, Michal Konecny <mkone...@redhat.com> wrote:
The New Hotness uses RPM version comparison for this and if this fails,
there isn't much we can do about it. See
https://github.com/fedora-infra/the-new-hotness/blob/2b3f7d7c2af847a48d190cab952125e7ccb97690/hotness/common/rpm.py#L32
if you want to look at how the compare method is implemented.

What's sad is that release-monitoring.org knows exactly which release is prerelease and which release is stable, so it's a shame that info gets lost somewhere before it manages to report a bug. Bug reports are nice, but some other mechanism for release notifications that doesn't lose the release information would be even better....

Michael

_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to