This would create a vast amount of bogus notifications and there are
multiple reasons why:
1) Editing the project in Anitya (this could create a really strange
versions, especially for custom backend)
2) Creating a new project in Anitya (the first check usually retrieves
large amount of new versions)
3) Not every project is checked for tarballs (there are plenty of
backends, that are checking tags or parsing html, which could be in some
cases anything, but versions)
4) Deleting versions in Anitya and retrieving them again (this could
create a large amount of new versions that are retrieved) - this is
needed if the project was incorrectly setup and needs to be edited
5) Incorrectly setup project in Anitya (this will just send you some
weird versions that don't need to be correct at all)
But this is the issue I plan to address in the future, because I
understand that the people want to be notified about every new version
released upstream not only latest. The issue here is to recognize
version that is really new and not something that was already reported,
just resend by Anitya. I needd to come with some solution that wouldn't
create massive amount of false warnings.
Right now The New Hotness is considered to help primarily with Rawhide
and the latest version of the project. I hope it's doing this service well.
Michal
On 09. 12. 21 21:23, Michael Catanzaro wrote:
I honestly don't understand what the problem is. Why not simply notify
whenever there is a new upstream tarball, regardless of what the
version looks like? Trying to compare versions is pointless because we
have as many as four different Fedora releases to maintain at any
given time and they could all require updates from different upstream
branches.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
