Re: Add a rule to have a compose when Fedora branched

[jkonecny@xxxxxxxxxx]

On Tue, 2019-09-17 at 16:33 +0200, Fabio Valentini wrote:

On Tue, Sep 17, 2019, 16:28 Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:

On 17. 09. 19 15:58, jkonecny@xxxxxxxxxx wrote:
> To make things even worse there was a switch to python 3.8 on Rawhide
> which wasn't really prepared (pylint did not worked).

I trust that your intentions were only the best when you wrote your e-mail, but
this statement kinda surprises me. The switch to Python 3.8 was very well
prepared and I consider it one of the smoothest switches to a new Python version
I can remember.

Pylint is never prepared for the switch. If something crucial is depending on
pylint, it should stop.

Also, IIRC, the failing rawhide composes at the time weren't even caused by the switch to python 3.8, at least not exclusively.

Fabio

Broken Rawhide composes are not the problem. When you have any compose in the history then you have at least something (even if it is not the newest). The problem is when you don't have any compose at all.

Jirka

_______________________________________________

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

_______________________________________________
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