Re: The New Hotness 1.0.0 deployed on production

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Dec 13, 2021 at 11:41 AM Michal Konecny <mkonecny@xxxxxxxxxx> wrote:
>
>
> Do you have an example? Because this is a bug. If the project doesn't
> have some strange versioning scheme the stable should be still
> considered newer than pre-release and the message should be emitted and
> processed by The New Hotness.

Here's an example:

https://release-monitoring.org/project/141635/

After getting notifications for the first 2.0.0-beta releases, I added
a version filter to exclude alpha;beta versions.
But upstream kept releasing versions 1.9.0, 1.9.1, 1.9.2, etc. after
that, which are not considered *newer* than the last 2.0.0-beta
version anitya saw, so we don't get bugs for them. So this is not a
problem with a strange versioning scheme, but with anitya not removing
versions from its database, I guess.

Fabio
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux