[prev in list] [next in list] [prev in thread] [next in thread]
List: python-dev
Subject: [Python-Dev] Currently working on the release of Python 3.8.0rc1
From: Łukasz_Langa <lukasz () langa ! pl>
Date: 2019-09-30 7:48:27
Message-ID: 507BEB88-1542-463E-9994-637D8522A6C8 () langa ! pl
[Download RAW message or body]
[Attachment #2 (multipart/signed)]
[Attachment #4 (multipart/alternative)]
Team,
amazing job on getting us back on track over the weekend.
Thank you
All release blockers and deferred release blockers solved. And there was =
relatively little additional activity on the branch -- as expected at =
this point! Thank you for this, it will help get the release candidate =
out on time.
I'm working on cutting RC1 today
Hopefully all sanity checks, as well as building the source tarball and =
the binary installers for macOS and Windows will all work out fine and =
we'll be seeing RC1 out tonight.
RC2 and the date of 3.8.0 gold
If we manage to avoid the need for RC2, we will be able to release 3.8.0 =
on October 14th. If we need an RC2, that will slip by a week. I hope we =
won't. Ideally RC1 should be identical codewise to 3.8.0.
To help our chances, please avoid any source-related activity on the 3.8 =
branch from now until the release of 3.8.0. Yes, that also counts for =
bug fixes unless they are critical. (Yeah, it might be a bit annoying =
but nobody wants to be the person who introduced a last minute =
regression in a major release.)
Note I didn't say I forbid any activity. I have no power over you, =
actually. More importantly though, I trust your judgement if you assess =
some bug is bad enough the fix absolutely has to get into 3.8.0. =
Moreover, I specifically said source-related activity because...
3.8.0 is important. To some users it will be the first and the last =
release in the 3.8 series they will see.
We need you to focus on the docs now
Are all your changes properly documented?
Did you notice other changes you know of to have insufficient =
documentation?
Can you help with the "What's New" document?
anxiously configure-&&-makingly y'rs
- =C5=81
[Attachment #7 (unknown)]
<html><head><meta http-equiv="Content-Type" content="text/html; \
charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
line-break: after-white-space;" class="">Team,<div class="">amazing job on getting us \
back on track over the weekend.</div><div class=""><br class=""></div><div \
style="font-size: 14px;" class=""><b class="">Thank you</b></div><div class="">All \
release blockers and deferred release blockers solved. And there was relatively \
little additional activity on the branch -- as expected at this point! Thank you for \
this, it will help get the release candidate out on time.</div><div class=""><br \
class=""></div><div style="font-size: 14px;" class=""><b class="">I'm working on \
cutting RC1 today</b></div><div class="">Hopefully all sanity checks, as well as \
building the source tarball and the binary installers for macOS and Windows will all \
work out fine and we'll be seeing RC1 out tonight.</div><div class=""><br \
class=""></div><div style="font-size: 14px;" class=""><b class="">RC2 and the date of \
3.8.0 gold</b></div><div class="">If we manage to avoid the need for RC2, we will be \
able to release 3.8.0 on October 14th. If we need an RC2, that will slip by a week. I \
hope we won't. Ideally RC1 should be identical codewise to 3.8.0.</div><div \
class=""><br class=""></div><div class="">To help our chances, please avoid any \
source-related activity on the 3.8 branch from now until the release of 3.8.0. Yes, \
that also counts for bug fixes unless they are critical. (Yeah, it might be a bit \
annoying but nobody wants to be the person who introduced a last minute regression in \
a major release.)</div><div class=""><br class=""></div><div class="">Note I didn't \
say I forbid any activity. I have no power over you, actually. More importantly \
though, I trust your judgement if you assess some bug is bad enough the fix \
absolutely has to get into 3.8.0. Moreover, I specifically said source-related \
activity because...</div><div class=""><br class=""></div><div class="">3.8.0 is \
important. To some users it will be the first and the last release in the 3.8 series \
they will see.</div><div class=""><br class=""></div><div style="font-size: 14px;" \
class=""><b class="">We need you to focus on the docs now</b></div><div class="">Are \
all your changes properly documented?</div><div class="">Did you notice other changes \
you know of to have insufficient documentation?</div><div class="">Can you help with \
the "What's New" document?</div><div class=""><br class=""></div><div \
class="">anxiously configure-&&-makingly y'rs</div><div class="">- \
Ł</div></body></html>
["signature.asc" (signature.asc)]
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE4/8oOcBIslwITevpsmmV4xAlBWgFAl2Rs0sACgkQsmmV4xAl
BWhJXQ//aLxHqjwcV1Vwr0T1BPMM+Upt1KF5L/5OwPcHEhXq1U0CZ8GI4E29+x8b
ymmPNe4s1TZmMMBgIGUkLAGfnTQnTXtQVGslyaSvUnzCzrAJaPCNt07SYbkprGko
zz82c88dW9GQA9iIBICyWe5lnjpAlLAET+duQmKOgGAhKCNSIJXZgLjtDGVByXhX
ADqX1yowiJGf//YSPofO2OB0cMRBDijEynpO30BWqDWN857rzFnaIds9Jo+zT8Y2
1kRgGPDrzc9pek3BbVWleJHmLhT4aoFRrO7KD1rhDEbYuf1aTOg18FFhVaAG8H1z
CG89c5egrw75KmWTr7hm/5cgDDAoVbqW5MO65QK8A9yntLVJTABq6iIOFXgZl5nq
wbuPmGD++iBU3iew7lPKPLAqaDyqvER0sDhxYY85gA4Jlp42N6YrKrYwZBvPW39w
owHecNL/1LSjcyHC2xo/T+bp1budBmyLa0+8Kg6a6t0pLGXNOqPshcE6wPIubB66
CicQXrlENpawNjy+HHEht05iQf+zp/zF1Yds3Fmz0YOH9A6HZXgfP3IIUxdn2r+k
iqDEv/ig/pw7b72xXnJUJznhfg9lgQory0xfzDshaSrUYDQkZcePckb1UaU44ZgA
AWmuiDYMp0YJhqwrfe7cKZqGOJFjkUD5ANVhFRAKMbuek6FjQoA=
=++v4
-----END PGP SIGNATURE-----
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-leave@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/ACMKEQNGK4FVUIZ6TYD5H26OSPIO5GSN/
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic