REVIEW NEEDED: Python 2 EOL press release and publication list
Hi Communications team! Changeset Consulting has been working on a press release for Python 2 EOL. Cc'ed in is the Changeset group working on this: Greg who has been working on this task and Sumana who has been overseeing. Please review the press release and publication list that will be approached with this press release. A few general notes: - Goal is to get this out this week. - Greg will work on a blog post (on pyfound) to publish at the same time as this press release. I have edits/suggestions to make for the press release: - After reviewing this with Ernest, we recommend linking to the branch status page so folks know they should migrate to a version that hasn't reached end-of-life (for example 3.2, 3.3, and 3.4 have already reached their end-of-life) - Such as "Users are urged to migrate to a supported version of Python 3 in order to benefit from tits many improvements, as well as to avoid potential security vulnerabilities in Python 2.x after April 2020. For the current status and status of Python 3 versions, see https://devguide.python.org/#status-of-python-branches” - Since the Steering Council reviewed this PR, a few more links were added (which is great!). The long Q&A is reflective of the Jan 2020 and April 2020 dates but the short Q&A link only refers to Jan 2020. We should probably update the short Q&A to reflect http://python-notes.curiousefficiency.org/en/latest/python3/questions_and_an... - Can we link to https://www.python.org/psf/ where it says what the PSF is? - Not sure if it is possible to list the date in ISO format: the year first, followed by month, then day - There seems to be a word (or words) missing after "CPython" in this sentence: "Going forward, Python 3 is the only major version the CPython will be actively maintained for bugs and security issues." Communication team: Please chime in with edits/suggestions. As mentioned earlier, the goal is to get this out this week. Thank you, Ewa ----------------------- *As a non-profit organization, the PSF depends on sponsorships and donations to support the Python community. Check out our Annual Impact Report for more details: https://www.python.org/psf/annual-report/2019/ <https://www.python.org/psf/annual-report/2019/>* *Please contribute to PSF; we can't continue our work without your support! https://www.python.org/psf/donations/ <https://www.python.org/psf/donations/>*
Hi all, I’ve reviewed the PDF and found only a few things, see the attached PDF with comments and replacement texts. Please let me know if that format doesn’t work for you so I can move the notes into the email thread instead. Regarding the distribution list, looking through the journalists/bloggers it seems this is mostly focused on English-speaking publications, do we intend to send this out to non-English outlets as well? If yes, do you want me to find out some where I reside (Germany)? Thanks, Jannis PS: Could we in the future do this in a Google Document or another shared word processor to simplify the review process?
On 17. Dec 2019, at 16:45, Ewa Jodlowska <ewa@python.org> wrote:
Hi Communications team!
Changeset Consulting has been working on a press release for Python 2 EOL. Cc'ed in is the Changeset group working on this: Greg who has been working on this task and Sumana who has been overseeing.
Please review the press release and publication list that will be approached with this press release.
A few general notes: • Goal is to get this out this week. • Greg will work on a blog post (on pyfound) to publish at the same time as this press release. I have edits/suggestions to make for the press release: • After reviewing this with Ernest, we recommend linking to the branch status page so folks know they should migrate to a version that hasn't reached end-of-life (for example 3.2, 3.3, and 3.4 have already reached their end-of-life) • Such as "Users are urged to migrate to a supported version of Python 3 in order to benefit from tits many improvements, as well as to avoid potential security vulnerabilities in Python 2.x after April 2020. For the current status and status of Python 3 versions, see https://devguide.python.org/#status-of-python-branches” • Since the Steering Council reviewed this PR, a few more links were added (which is great!). The long Q&A is reflective of the Jan 2020 and April 2020 dates but the short Q&A link only refers to Jan 2020. We should probably update the short Q&A to reflect http://python-notes.curiousefficiency.org/en/latest/python3/questions_and_an... • Can we link to https://www.python.org/psf/ where it says what the PSF is? • Not sure if it is possible to list the date in ISO format: the year first, followed by month, then day • There seems to be a word (or words) missing after "CPython" in this sentence: "Going forward, Python 3 is the only major version the CPython will be actively maintained for bugs and security issues." Communication team: Please chime in with edits/suggestions. As mentioned earlier, the goal is to get this out this week.
Thank you,
Ewa
----------------------- As a non-profit organization, the PSF depends on sponsorships and donations to support the Python community. Check out our Annual Impact Report for more details: https://www.python.org/psf/annual-report/2019/ Please contribute to PSF; we can't continue our work without your support! https://www.python.org/psf/donations/ <Python 2 Sunset Press Release -- Draft 2012-16.pdf><Python Press List.xlsx>_______________________________________________ Psf-communications mailing list -- psf-communications@python.org To unsubscribe send an email to psf-communications-leave@python.org https://mail.python.org/mailman3/lists/psf-communications.python.org/
The draft PDF generally looks good to me. I have some small edits I would make on the version Jannis just sent, but I'll have to do that a bit later when I can convert and edit the PDF. I agree that a Google Doc would definitely be easier to edit in the future.
PS: Could we in the future do this in a Google Document or another shared word processor to simplify the review process?
Best, Marlene On Tue, Dec 17, 2019 at 6:33 PM Jannis Leidel <jannis.leidel@pyfound.org> wrote:
Hi all,
I’ve reviewed the PDF and found only a few things, see the attached PDF with comments and replacement texts. Please let me know if that format doesn’t work for you so I can move the notes into the email thread instead.
Regarding the distribution list, looking through the journalists/bloggers it seems this is mostly focused on English-speaking publications, do we intend to send this out to non-English outlets as well? If yes, do you want me to find out some where I reside (Germany)?
Thanks, Jannis
PS: Could we in the future do this in a Google Document or another shared word processor to simplify the review process?
On 17. Dec 2019, at 16:45, Ewa Jodlowska <ewa@python.org> wrote:
Hi Communications team!
Changeset Consulting has been working on a press release for Python 2 EOL. Cc'ed in is the Changeset group working on this: Greg who has been working on this task and Sumana who has been overseeing.
Please review the press release and publication list that will be approached with this press release.
A few general notes: • Goal is to get this out this week. • Greg will work on a blog post (on pyfound) to publish at the same time as this press release. I have edits/suggestions to make for the press release: • After reviewing this with Ernest, we recommend linking to the branch status page so folks know they should migrate to a version that hasn't reached end-of-life (for example 3.2, 3.3, and 3.4 have already reached their end-of-life) • Such as "Users are urged to migrate to a supported version of Python 3 in order to benefit from tits many improvements, as well as to avoid potential security vulnerabilities in Python 2.x after April 2020. For the current status and status of Python 3 versions, see https://devguide.python.org/#status-of-python-branches” • Since the Steering Council reviewed this PR, a few more links were added (which is great!). The long Q&A is reflective of the Jan 2020 and April 2020 dates but the short Q&A link only refers to Jan 2020. We should probably update the short Q&A to reflect http://python-notes.curiousefficiency.org/en/latest/python3/questions_and_an... • Can we link to https://www.python.org/psf/ where it says what the PSF is? • Not sure if it is possible to list the date in ISO format: the year first, followed by month, then day • There seems to be a word (or words) missing after "CPython" in this sentence: "Going forward, Python 3 is the only major version the CPython will be actively maintained for bugs and security issues." Communication team: Please chime in with edits/suggestions. As mentioned earlier, the goal is to get this out this week.
Thank you,
Ewa
----------------------- As a non-profit organization, the PSF depends on sponsorships and donations to support the Python community. Check out our Annual Impact Report for more details: https://www.python.org/psf/annual-report/2019/ Please contribute to PSF; we can't continue our work without your support! https://www.python.org/psf/donations/ <Python 2 Sunset Press Release -- Draft 2012-16.pdf><Python Press List.xlsx>_______________________________________________ Psf-communications mailing list -- psf-communications@python.org To unsubscribe send an email to psf-communications-leave@python.org https://mail.python.org/mailman3/lists/psf-communications.python.org/
_______________________________________________ Psf-communications mailing list -- psf-communications@python.org To unsubscribe send an email to psf-communications-leave@python.org https://mail.python.org/mailman3/lists/psf-communications.python.org/
Jannis Leidel <jannis.leidel@pyfound.org> writes:
I’ve reviewed the PDF and found only a few things, see the attached PDF with comments and replacement texts. Please let me know if that format doesn’t work for you so I can move the notes into the email thread instead.
That might be easier, please? Especially for the items where you're asking questions as opposed to suggesting a specific edit to make.
Regarding the distribution list, looking through the journalists/bloggers it seems this is mostly focused on English-speaking publications, do we intend to send this out to non-English outlets as well? If yes, do you want me to find out some where I reside (Germany)?
Yes, please! Ideally we want to send a personalized email. So if you can supply a name and email for someone at the publication, we can definitely use it. Also: I will share a little suggested template email that any of you can use, to give a more casual heads-up to people in your network, if you want.
PS: Could we in the future do this in a Google Document or another shared word processor to simplify the review process?
Of course it's not my place to say how you should do this in the future. :) In this case: We don't have much time, to release this week. Google Docs can be confusing when too many people edit a doc simultanously. As a result, I am happy to act as the human editor who is responsible for accumulating suggestions and trying to make a consistent, correct result.
On 17. Dec 2019, at 18:36, Greg Hendershott <mail@greghendershott.com> wrote:
Jannis Leidel <jannis.leidel@pyfound.org> writes:
I’ve reviewed the PDF and found only a few things, see the attached PDF with comments and replacement texts. Please let me know if that format doesn’t work for you so I can move the notes into the email thread instead.
That might be easier, please? Especially for the items where you're asking questions as opposed to suggesting a specific edit to make.
Makes sense. Here it is: 1. The subtitle says: "CPython core development community urging users to migrate to Python 3 as it will be the only version that will be updated for bugs and security vulnerabilities.” And I'm wondering whether that is really accurate since I'm sure some Python vendors may or may not decide to continue to fix bugs and sec vulnerabilities? 2. We should either use “Python 3.X” or “Python 3” (I’d prefer the latter) in the messaging to not confuse people. 3. “We are so grateful the countless volunteers..” -> “We are so grateful for the countless volunteers..” 4. The paragraph about the improvements in Python 3 is quite long, I’d cut it in smaller sentences: “There is ground-up support for Unicode and internationalization; it better expresses common idioms and patterns, which in code makes it easier to read and reason about; and improvements in concurrency, fault handling, testing, and debugging provides developers with the opportunity to create more robust and secure applications.” -> “There is ground-up support for Unicode and internationalization. It better expresses common idioms and patterns, which in code makes it easier to read and reason about. Improvements in concurrency, error handling, testing, and debugging provides developers with the opportunity to create more robust and secure applications.” 5. “Going forward, Python 3 is the only major version the CPython will be actively maintained for bugs and security issues.” -> “Going forward, Python 3 is the only major version of CPython that will be actively maintained for bugs and security issues.”
Regarding the distribution list, looking through the journalists/bloggers it seems this is mostly focused on English-speaking publications, do we intend to send this out to non-English outlets as well? If yes, do you want me to find out some where I reside (Germany)?
Yes, please! Ideally we want to send a personalized email. So if you can supply a name and email for someone at the publication, we can definitely use it.
Heise Publishing (Big German publisher): - Matthias Parbel map@heise.de (iX computer magazine and heise online) - developer@heise.de (heise Developer) - Jan Mahn jam@ct.de (ct computer magazine)
Also: I will share a little suggested template email that any of you can use, to give a more casual heads-up to people in your network, if you want.
That would be very useful, thank you!
PS: Could we in the future do this in a Google Document or another shared word processor to simplify the review process?
Of course it's not my place to say how you should do this in the future. :)
In this case: We don't have much time, to release this week. Google Docs can be confusing when too many people edit a doc simultanously. As a result, I am happy to act as the human editor who is responsible for accumulating suggestions and trying to make a consistent, correct result.
Makes sense, thanks for sending it around in the first place!
Hi, Jannis. Thank you very much!
1. The subtitle says: "CPython core development community urging users to migrate to Python 3 as it will be the only version that will be updated for bugs and security vulnerabilities.”
And I'm wondering whether that is really accurate since I'm sure some Python vendors may or may not decide to continue to fix bugs and sec vulnerabilities?
I 100% agree with all your other suggestions (see below) and just incorporated them (will share new version shortly). About your question here: In my opinion, this sentence is accurate because it is talking about what the CPython core development community plans to do. What other people do, with open source, is of course up to them, and they can announce their own plans if they wish. Meanwhile, this is what we're announcing. Also I think it is acceptable for the subtitle to be a _little_ simplified in the service of supporting our main "call to action" here: "Please migrate to Python 3!". Finally, although I could edit the subtitle to add some qualification or nuance, I worry it might end up becoming a bit long and confusing? Those are my points in favor of keeping it as-is. However of course please let me know if you disagree? And if so, what new text you recommend?
2. We should either use “Python 3.X” or “Python 3” (I’d prefer the latter) in the messaging to not confuse people.
Thanks! Changed.
3. “We are so grateful the countless volunteers..” -> “We are so grateful for the countless volunteers..”
Thanks! Changed.
4. The paragraph about the improvements in Python 3 is quite long, I’d cut it in smaller sentences: “There is ground-up support for Unicode and internationalization; it better expresses common idioms and patterns, which in code makes it easier to read and reason about; and improvements in concurrency, fault handling, testing, and debugging provides developers with the opportunity to create more robust and secure applications.” ->
“There is ground-up support for Unicode and internationalization. It better expresses common idioms and patterns, which in code makes it easier to read and reason about. Improvements in concurrency, error handling, testing, and debugging provides developers with the opportunity to create more robust and secure applications.”
Thanks! Changed.
5. “Going forward, Python 3 is the only major version the CPython will be actively maintained for bugs and security issues.” -> “Going forward, Python 3 is the only major version of CPython that will be actively maintained for bugs and security issues.”
Thanks! Changed.
Heise Publishing (Big German publisher):
- Matthias Parbel map@heise.de (iX computer magazine and heise online) - developer@heise.de (heise Developer) - Jan Mahn jam@ct.de (ct computer magazine)
Thank you! I will add to the distribution list. Best regards, Greg
Thank you. I updated to include all of those changes. I'll wait a bit to accumulate more suggestions from other folks, then share a new version. Ewa Jodlowska <ewa@python.org> writes:
I have edits/suggestions to make for the press release:
- After reviewing this with Ernest, we recommend linking to the branch status page so folks know they should migrate to a version that hasn't reached end-of-life (for example 3.2, 3.3, and 3.4 have already reached their end-of-life) - Such as "Users are urged to migrate to a supported version of Python 3 in order to benefit from tits many improvements, as well as to avoid potential security vulnerabilities in Python 2.x after April 2020. For the current status and status of Python 3 versions, see https://devguide.python.org/#status-of-python-branches” - Since the Steering Council reviewed this PR, a few more links were added (which is great!). The long Q&A is reflective of the Jan 2020 and April 2020 dates but the short Q&A link only refers to Jan 2020. We should probably update the short Q&A to reflect http://python-notes.curiousefficiency.org/en/latest/python3/questions_and_an... - Can we link to https://www.python.org/psf/ where it says what the PSF is? - Not sure if it is possible to list the date in ISO format: the year first, followed by month, then day - There seems to be a word (or words) missing after "CPython" in this sentence: "Going forward, Python 3 is the only major version the CPython will be actively maintained for bugs and security issues."
Hi, all. Attached please find an updated version of the press release. This incorporates the feedback provided so far, from Ewa and Jannis. I'd be grateful if you could provide any more feedback -- or approval -- as soon as possible? - Our deadline is to post this live Friday (2 days). - If possible it would be wonderful to approve the press release by end of Thursday (tomorrow). That way, Friday we could focus fully on coordinating a smooth release and distribution to the list of publications and bloggers. Thank you! Best regards, Greg
p.s. Just moments after sending :-( I noticed a small typo introduced from the previous round of feedback: For the current status and status of Python 3 versions, see .... I already fixed that for the next version: For the current status of Python 3 versions, see .... Greg Hendershott <mail@greghendershott.com> writes:
Hi, all.
Attached please find an updated version of the press release.
This incorporates the feedback provided so far, from Ewa and Jannis.
I'd be grateful if you could provide any more feedback -- or approval -- as soon as possible?
- Our deadline is to post this live Friday (2 days).
- If possible it would be wonderful to approve the press release by end of Thursday (tomorrow).
That way, Friday we could focus fully on coordinating a smooth release and distribution to the list of publications and bloggers.
Thank you!
Best regards, Greg
participants (4)
-
Ewa Jodlowska -
Greg Hendershott -
Jannis Leidel -
Marlene Mhangami