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
"Date" of what's new is confusing #73905
Comments
See https://docs.python.org/3/whatsnew/3.6.html At top: :Release: |release| This |today| is replaced with day when HTML is build (like "Last updated:" in footer). This is near to the date this page is modified last on docs.python.org, until clean rebuild happens. How about replacing |today| to Python 3.6.0 release date, or removing the ":Date: |today|" line? |
It's a bit confusing but: is the URL for the current 3.6 branch, in other words, what will be in the next 3.6 release. These are rebuilt as changes are checked in. (which is linked from https://www.python.org/doc/versions/) is the URL for the docs corresponding to the 3.6.0 release. These are built at release time and then never change. Does that help? |
"next 3.6 release" means 3.6.1?
There are some commit for fixing something after 3.6.0 released. So I still this ":Date:" should be release date, or removed. |
Sorry, I disagree. I think the point of adding these directives is that shows for what release of 3.6.x they apply. It is expected that the What's New documents may be updated during the lifecycle of a major release and having the release and date there lets the reader know that they are update. For example, at the moment https://docs.python.org/3.6/whatsnew/3.6.html shows: What’s New In Python 3.6 which is correct. |
https://docs.python.org/3.7/whatsnew/3.6.html shows: Is it make sense for you? |
Additonally, unlike "changelog", "What's New" only shows difference between 3.5 and 3.6. It won't be updated to describe changes between 3.6.0 and 3.6.1. |
That's not always true. There are occasionally changes made in the What's New document for maintenance releases. See, for example, https://docs.python.org/3.5/whatsnew/3.5.html. You'll find references to 3.5.1 and 3.5.2 there. If it's truly bothering people, a better solution is to just remove the release and date directives. They aren't there for earlier releases. We can live without them. |
I'm sorry, I was wrong. https://docs.python.org/3.5/whatsnew/3.5.html asyncio has "Updates in 3.5.1:" section. So is it OK to just removing Date and Release field? |
Heh, it looks like we agree! |
I believe this can be closed as 'fixed'? |
Well, it *was* fixed! But then I reintroduced the boilerplate when I created the 3.7 and 3.8 whatsnew files - now fixed. Thanks for the reminder! |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: