Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 1.7k
Add Topic for release schedule PEPs#2669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Conversation
Release PEPs are a pretty unusual kind of PEP and it's useful to me to have them all listed together. Happy to adjust the name of the topic if desired. I took the opportunity to adjust the status of a few release PEPs. Now all releases for EOL versions are Final (3.5 was previously Active), and all releases for released versions are Active (3.10 was still draft). 3.11 remains Draft as 3.11 has not yet been released.
Uh oh!
There was an error while loading. Please reload this page.
hugovk commented Jun 25, 2022
This would be useful. Preview: https://pep-previews--2669.org.readthedocs.build/topic/releases/ Please also include PEP 693 for Python 3.12. |
AA-Turner commented Jun 25, 2022
"Release Schedule" would make sense to me, spaces are allowed within the topic names. A |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
CAM-Gerlach commented Jun 27, 2022 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
But then the URL to the topic page wouldn't match the lowercase/case insensitive topic name; either it would have to have |
pradyunsg commented Jun 27, 2022
My 2 cents: "Release Schedule" or "Release" are better names since they'll read better in the page heading ("Release Schedule PEPs"/"Release PEPs"). Right now, it looks to me like there's a grammatical error in there. |
pradyunsg commented Jun 27, 2022
It might also make sense to retitle "Other Informational PEPs" to "Informational PEPs" on all pages, since having an "Other" in the first heading seems wrong (as is the case with this topic index right now). |
CAM-Gerlach commented Jun 28, 2022
👍 to "Release" |
JelleZijlstra commented Jul 1, 2022
The latest pushes add the PEPs I missed (thanks Adam for digging those up!), address other feedback, and rename the header to "Release". |
CAM-Gerlach left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I didn't mention it before, but like on #2670 , I suggest using a consistant header order with the existing packaging-topic PEPs, i.e. Topic after Type.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
CAM-Gerlach left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @JelleZijlstra
Release PEPs are a pretty unusual kind of PEP and it's useful to me to have
them all listed together. Happy to adjust the name of the topic if desired.
I took the opportunity to adjust the status of a few release PEPs. Now all
releases for EOL versions are Final (3.5 was previously Active), and all
releases for released versions are Active (3.10 was still draft). 3.11 remains
Draft as 3.11 has not yet been released.