Re: Python 3.11 final release might be delayed to December

[Miro Hrončok]

On 05. 07. 22 13:17, Miro Hrončok wrote:

Hello,
forwarding this  message to Fedora.

Will know more by the end of this week -- we might need to consider reverting 
back to Python 3.10 if we don't want to ship Fedora 37 GA with a beta version 
of Python :(


The fourth beta is out.

"As the requirements to continue with the regular schedule are met, we are 
going to still target the final release of Monday, 2022-10-03."


https://mail.python.org/archives/list/python-...@python.org/message/VD7YNBVMEPKZLRA6VOTYAQYTEZPDH6Q7/

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
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/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Python 3.11 final release might be delayed to December

[Miro Hrončok]

On 05. 07. 22 13:17, Miro Hrončok wrote:

Hello,
forwarding this  message to Fedora.

Will know more by the end of this week -- we might need to consider reverting 
back to Python 3.10 if we don't want to ship Fedora 37 GA with a beta version 
of Python :(


Fedora 37 mass rebuild is planned for 2022-07-20 -- I will make sure we know 
what to do by then.


Too bad we haven't known this before we started the 3.11 mass rebuild :/


I've opened a FESCo issue: https://pagure.io/fesco/issue/2825


 Forwarded Message 
Subject: [Python-Dev] [Release] Status of Python 3.11 release
Date: Mon, 4 Jul 2022 23:36:39 +0100
From: Pablo Galindo Salgado 
To: Python Dev , python-committers 





Hi everyone,

# TLDR

We may be pushing the final release until December if the stability of Python 
3.11 doesn't improve.


# Long Explanation

Unfortunately, we cannot still release the next Python 3.11 beta release 
(3.11.0b4) because we still have a bunch
of pending release blockers. Unfortunately, this is still after several 
preexisting release blockers have been fixed,
some of them being discovered after I sent my last update. These are the 
current release blockers:


https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Arelease-blocker+label%3A3.11+ 
<https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Arelease-blocker+label%3A3.11+> 



We also have some deferred blockers (some of them should actually be release 
blockers):


https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Adeferred-blocker+label%3A3.11 
<https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Adeferred-blocker+label%3A3.11> 



Due to this and the fact that we are already 3 weeks delayed in the release 
schedule, the current stability of Python 3.11 is not as good
as it is supposed to be at this stage of the release schedule and more testing 
from end-users and library authors is required. After
discussing with the Steering Council, we are considering delaying the final 
release until December to allow for two more beta releases.

This is how we are going to proceed:

* If the current release blockers are not fixed by the end of this week, two 
more betas will be released (1 month per beta) and

we will *definitely* delay the final release until December.
* If the current release blockers are fixed we will proceed to release Python 
3.11.0b4 on Monday. We will target the current release
date (Monday, 2022-10-03) but if more release blockers that affect fundamental 
parts of the Python interpreter or the standard libraries
are raised, the release team will still consider adding two more betas nd 
pushing the final release to December.


One of the goals that we are going to try to achieve from the release team is 
that no substantial code changes are added between the last
beta and the first release candidate. This is so all the fixes that affect 
fundamental parts of the interpreter or the standard library can be
tested by end-users before the first release candidate is released (and not 
with it). This is also partially because once we release the first release
candidate, the ABI will be frozen and certain kinds of fixes will be more 
complicated.


Hopefully, this addresses some of you that have reached out with concerns over 
the stability of Python 3.11 and the release schedule.


I understand that delaying the release until December will complicate things 
for some Linux distributions and will affect end users and redistributors
targeting the original release, but please understand that our 
responsibility in the release team after all is to guarantee a stable final 
release
above all and unfortunately, we don't currently have the confidence that we 
would like given the current state of the release process.


Please do not hesitate in reaching out if you have any questions or concerns.

Thanks, everyone for your help and understanding and thanks a lot to all of you 
for your great work!


Cheers from cloudy London,
Pablo Galindo Salgado


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
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/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Python 3.11 final release might be delayed to December

[Miro Hrončok]

Hello,
forwarding this  message to Fedora.

Will know more by the end of this week -- we might need to consider reverting 
back to Python 3.10 if we don't want to ship Fedora 37 GA with a beta version 
of Python :(


Fedora 37 mass rebuild is planned for 2022-07-20 -- I will make sure we know 
what to do by then.


Too bad we haven't known this before we started the 3.11 mass rebuild :/


 Forwarded Message 
Subject:[Python-Dev] [Release] Status of Python 3.11 release
Date:   Mon, 4 Jul 2022 23:36:39 +0100
From:   Pablo Galindo Salgado 
To: 	Python Dev , python-committers 





Hi everyone,

# TLDR

We may be pushing the final release until December if the stability of Python 
3.11 doesn't improve.


# Long Explanation

Unfortunately, we cannot still release the next Python 3.11 beta release 
(3.11.0b4) because we still have a bunch
of pending release blockers. Unfortunately, this is still after several 
preexisting release blockers have been fixed,
some of them being discovered after I sent my last update. These are the 
current release blockers:


https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Arelease-blocker+label%3A3.11+ 



We also have some deferred blockers (some of them should actually be release 
blockers):


https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Adeferred-blocker+label%3A3.11 



Due to this and the fact that we are already 3 weeks delayed in the release 
schedule, the current stability of Python 3.11 is not as good
as it is supposed to be at this stage of the release schedule and more testing 
from end-users and library authors is required. After
discussing with the Steering Council, we are considering delaying the final 
release until December to allow for two more beta releases.

This is how we are going to proceed:

* If the current release blockers are not fixed by the end of this week, two 
more betas will be released (1 month per beta) and

we will *definitely* delay the final release until December.
* If the current release blockers are fixed we will proceed to release Python 
3.11.0b4 on Monday. We will target the current release
date (Monday, 2022-10-03) but if more release blockers that affect fundamental 
parts of the Python interpreter or the standard libraries
are raised, the release team will still consider adding two more betas nd 
pushing the final release to December.


One of the goals that we are going to try to achieve from the release team is 
that no substantial code changes are added between the last
beta and the first release candidate. This is so all the fixes that affect 
fundamental parts of the interpreter or the standard library can be
tested by end-users before the first release candidate is released (and not 
with it). This is also partially because once we release the first release
candidate, the ABI will be frozen and certain kinds of fixes will be more 
complicated.


Hopefully, this addresses some of you that have reached out with concerns over 
the stability of Python 3.11 and the release schedule.


I understand that delaying the release until December will complicate things 
for some Linux distributions and will affect end users and redistributors
targeting the original release, but please understand that our 
responsibility in the release team after all is to guarantee a stable final release
above all and unfortunately, we don't currently have the confidence that we 
would like given the current state of the release process.


Please do not hesitate in reaching out if you have any questions or concerns.

Thanks, everyone for your help and understanding and thanks a lot to all of you 
for your great work!


Cheers from cloudy London,
Pablo Galindo Salgado
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
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/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora 34 testers needed: Please karma Python 3.9.9 update

[Miro Hrončok]

Hello testers.

We have a Python 3.9.9 update for Fedora 34:

https://bodhi.fedoraproject.org/updates/FEDORA-2021-e152ce5f31

Don't be scared by the long thread of discussion there, there were some 
problems with 3.9.8 and those are now fixed.


The update for Python 3.9.9 has reached updates-testing 2 weeks ago, but so far 
has only received +2 karma. I would be happier if more Fedora users tested it.


Thanks,
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
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/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 32: Python 3.8.8

[Miro Hrončok]

> Hello,
> we have updated the main Python from 3.8.7 to 3.8.8 in Fedora 32, but since 
> this 
> never went trough rawhide or Fedora 33 (already at 3.9), I wanted it to 
> receive 
> some karma before pushing the update.
> 
> However, after 14 days, it only gained +2.
> 
> If you run Fedora 32, please update Python from updates-testing and after a 
> few 
> days, report back via karma if your system is fully functional. Thanks.
> 
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-88d9d29680

This is still a valid request for help. Thanks.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
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/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Install timescaledb in Fodora34 Postgresql-13 failed.

[Miro Hrončok]

https://bodhi.fedoraproject.org/updates/FEDORA-2021-2a2ad12d9e
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
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/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora 32: Python 3.8.8

[Miro Hrončok]

Hello,
we have updated the main Python from 3.8.7 to 3.8.8 in Fedora 32, but since this 
never went trough rawhide or Fedora 33 (already at 3.9), I wanted it to receive 
some karma before pushing the update.


However, after 14 days, it only gained +2.

If you run Fedora 32, please update Python from updates-testing and after a few 
days, report back via karma if your system is fully functional. Thanks.


https://bodhi.fedoraproject.org/updates/FEDORA-2021-88d9d29680

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
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/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Python 3.9.0rc2 Fedora 33 update

[Miro Hrončok]

On 18. 09. 20 11:48, Miro Hrončok wrote:

Hello.

Python 3.9.0rc2, the last preview before the final release of Python 3.9.0 has 
been released yesterday.


The Fedora 33 update is at:

https://bodhi.fedoraproject.org/updates/FEDORA-2020-78bb031321


Should I try to get a freeze exception and get it to Fedora 33 Beta?

Pros:

We would test Fedora 33 Beta with Python that is close to identical to the one 
in Fedora 33 Final.


Cons:

If there is a regression, we could break Beta prior to its release.


I've actually proposed it, so the discussion can happen while 
approving/rejecting it:


https://bugzilla.redhat.com/show_bug.cgi?id=1880596

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
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/test@lists.fedoraproject.org

Python 3.9.0rc2 Fedora 33 update

[Miro Hrončok]

Hello.

Python 3.9.0rc2, the last preview before the final release of Python 3.9.0 has 
been released yesterday.


The Fedora 33 update is at:

https://bodhi.fedoraproject.org/updates/FEDORA-2020-78bb031321


Should I try to get a freeze exception and get it to Fedora 33 Beta?

Pros:

We would test Fedora 33 Beta with Python that is close to identical to the one 
in Fedora 33 Final.


Cons:

If there is a regression, we could break Beta prior to its release.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
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/test@lists.fedoraproject.org

Re: Proposal to change ARM Release Blocking Criteria - Drop XFCE (32bit), Add Workstation(64bit)

[Miro Hrončok]

> Proposed changes to the Desktop release criteria for ARM and AArch64 in 
> Fedora 32:
>  * drop Xfce on 32-bit ARM from release blocking desktops
>  * add Workstation on AArch64 to release blocking desktops

I am not following recent developments of chap arm based mini computers (read: 
Raspberry Pis and alike), hence my question might be a bit stupid here, but 
isn't Workstation a bit too resource-consuming for devices our users are likely 
to run Fedora "desktop" on? I'm fine if we are targeting the AArch64 based 
laptops, but are we OK with recommending either Workstation or non-bocking 
spins for arm devices with less than 4GB RAM?
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
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/test@lists.fedoraproject.org

Anyone running Fedora 29? python3 update needs karma

[Miro Hrončok]

Hey,

I've created a python3 Fedora 29 update 3 weeks ago:

https://bodhi.fedoraproject.org/updates/FEDORA-2019-60a1defcd1

I don't want to push it without a single user giving feedback, however it is a 
security update, so I don't want to keep it in testing forever.


Anyone still running F29 who could update to this python3 version and run the 
system for couple days?


Thanks.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
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/test@lists.fedoraproject.org

Fedora 29 Python Classroom Lab testers needed

[Miro Hrončok]

Hi.

The Fedora 29 Python Classroom Lab was not built for the proper Fedora 29 
release date.


We now have some candidates builds to test, so I'm looking for volunteers to 
help uncover issues.


https://pagure.io/releng/issue/7922

GNOME https://koji.fedoraproject.org/koji/taskinfo?taskID=32659167
Vagrant https://koji.fedoraproject.org/koji/taskinfo?taskID=32670129
Arm https://koji.fedoraproject.org/koji/taskinfo?taskID=32660565

See https://fedoraproject.org/wiki/Changes/PythonClassroomLab#How_To_Test

Thanks for help.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-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/test@lists.fedoraproject.org