On 21.5.2018 13:39, Petr Viktorin wrote:
Hello!
At PyCon US 2018, Łukasz Langa, the release manager for Python 3.7, told
me that he'd like to collect data about Release Candidates for point
releases (3.x.y). The idea is that if these aren't being tested and
aren't revealing bugs, it would make sense to stop releasing them.
What we might do is to prep the rc bump in copr, mass rebuild everything
there to see test failures.
The problem with this approach is that someone has to do this and even
if scripted, there are packages, where the test suites:
* fail in copr only (meh)
* fail for unrelated updates in rawhide (i.e. glibc)
So all the buildlogs of packages that fail to build would need manual
inspection. I don't think we have time/people to do this.
Also, the obvious imperfection here is also the fact that not all bugs
are found by running test suites.
What we could do as a minimal effort solution is to prep the rc in
pagure PR and at least see the test failures of CPython itself. This
could discover problems in the RCs as well as in Fedora. Earlier than
now nevertheless. As we generally update to new patch releases, we'd
need to fix those failures later anyway.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
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/python-devel@lists.fedoraproject.org/message/IVDQPW2VFIGVKVNLNJXA4ASQI76NF3JA/
