Dne 23. 05. 19 v 9:00 Michal Konecny napsal(a):
> Hi everybody,
>
> I want to announce that the-new-hotness was updated from 0.10.1 to
> 0.11.2 on production.
> The-new-hotness is consuming messages from Anitya and creating
> bugzilla bugs to notify packagers about new versions of packages.


Nice. Thx.

However, so far I have seen just some error reports such as:


https://bugzilla.redhat.com/show_bug.cgi?id=1560983#c5

https://bugzilla.redhat.com/show_bug.cgi?id=1668453#c2

https://bugzilla.redhat.com/show_bug.cgi?id=1668957#c16


Hard to tell what they are about. They do not provide enough information
to understand where the problem is. Unless you can provide better error
messages and log, I'd be better if such comments are not submitted at all.


Vít


>
> Main changes in this update are
> * migration from fedmsg <http://fedmsg.com/> to Fedora messaging
> <https://github.com/fedora-infra/fedora-messaging>
> * moving the-new-hotness from VM to OpenShift
> * removing python 2 support (the-new-hotness is now tested only in
> python 3)
>
> Full changelog could be found here
> https://github.com/fedora-infra/the-new-hotness/releases/tag/0.11.0
> https://github.com/fedora-infra/the-new-hotness/releases/tag/0.11.1
> https://github.com/fedora-infra/the-new-hotness/releases/tag/0.11.2
>
> Regards,
> mkonecny
>
>
> _______________________________________________
> infrastructure mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[email protected]
_______________________________________________
infrastructure mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to