On 17. 06. 19 21:03, Miro Hrončok wrote:
Hello,
When I filed the Python 3.8 [change] for Fedora 31, we knew that the schedule
would be tight.
For that very reason, we have not yet started to build for Python 3.8 in a f31
side tag, but instead we've only been doing it in [copr] so far.
The
On 17. 06. 19 22:12, Fabio Valentini wrote:
- right after the F32 branching (2019-08-13 according to the [schedule]), we
would start with the side tag builds
This is probably a typo, you must mean "just after the F31 branching", right?
Yes! F31 branching.
--
Miro Hrončok
--
Phone: +4207779
On Mon, Jun 17, 2019 at 9:52 PM Miro Hrončok wrote:
>
> Hello,
>
> When I filed the Python 3.8 [change] for Fedora 31, we knew that the schedule
> would be tight.
>
> For that very reason, we have not yet started to build for Python 3.8 in a f31
> side tag, but instead we've only been doing it in
On 17. 06. 19 21:41, Ben Cotton wrote:
Thanks for bringing this up, Miro.
On Mon, Jun 17, 2019 at 3:03 PM Miro Hrončok wrote:
- there are ~200 build failures that block this, tracked on [bugzilla]
I did a spot check of a few of the BZs and it looks like some of those
build failures are u
Thanks for bringing this up, Miro.
On Mon, Jun 17, 2019 at 3:03 PM Miro Hrončok wrote:
> - there are ~200 build failures that block this, tracked on [bugzilla]
I did a spot check of a few of the BZs and it looks like some of those
build failures are unrelated to Python 3.8 but are due to othe
Hello,
When I filed the Python 3.8 [change] for Fedora 31, we knew that the schedule
would be tight.
For that very reason, we have not yet started to build for Python 3.8 in a f31
side tag, but instead we've only been doing it in [copr] so far.
The mass rebuild happens on 2019-07-24, accord
