[python-committers] Re: Save the date: Virtual Core Dev Sprint Oct 19-23, 2020

[Mariatta]

As an update, I've created the python/core-sprint
repo to give you all visibility of
what we're up to.
You can open an issue there if you have any suggestions or questions about
the sprint.




On Thu, Aug 6, 2020 at 9:06 PM Mariatta  wrote:

> Please save the date for this year's core dev sprint, to take place
> virtually online from Oct 19 - 23, 2020.
>
> The sprint is being organized by myself and Kyle Stanley, with help from
> Ewa Jodlowska.
>
> We are still in the early planning stage, and just wanted to give you all
> a heads up so you can plan accordingly.
>
> We will keep you posted once we have more details on how the virtual
> sprint will work and how to sign up. In the meantime, if you have
> questions, concerns, or suggestions about the sprint, you can reply to this
> thread or start a new discussion on Discourse.
>
> In case you're not familiar about the core dev sprint, this is normally a
> weeklong (5 work days) sprint in person, where we would have focus time to
> work on CPython, finish your PEPs, review pull requests, etc.
>
> You can read about past core dev sprints here:
> Core dev sprint 2019
> 
> Core Dev sprint 2018
> 
>
> Thanks for all your contributions to CPython! I hope that you would plan
> to participate  from wherever you are!
>
> - Mariatta
>
>
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/ERLBYUF4MKPBACTI3Z3PJ7HWCPB26FY4/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Reminder: this coming Monday, Aug 10 is the planned date for Python 3.9.0rc1

[Łukasz Langa]

Entering the release candidate phase is an exciting and necessary step towards 
releasing a production-grade 3.9.0.

At this stage stability is of utmost importance. That's why the development 
process described in our Dev Guide specifies that "a branch preparing for an RC 
release can only have bugfixes applied that have been reviewed by other core 
developers". See more at 
https://devguide.python.org/devcycle/#release-candidate-rc

Note that due to the new PEP 602-compliant release calendar we are planning to 
have two release candidates: the first this coming Monday, August 10th, and the 
second on September 14th. As a reminder: expanding the RC phase was done to 
help operating system distributors include the latest release of Python in 
their own Autumn releases. To make it work, we need approach the release 
candidates with as much care as we will put into 3.9.0 itself.

Lastly, and this is a little embarrassing to admit, my laptop is being serviced 
by Apple at the moment due to a swollen battery. I'm ready to make the release 
without it should it not return by Monday. However, in case it turns out to be 
impossible, I'll let you know in a separate e-mail.

-- 
Best regards,
Łukasz Langa___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/ES2ZJ7GUSTZMJLP3UORQHQEWWHZRDP7H/
Code of Conduct: https://www.python.org/psf/codeofconduct/