This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: "What's New in Python" should have initial release date on heading
Type: enhancement Stage:
Components: Documentation Versions: Python 3.2, Python 3.3, Python 2.7
process
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, eric.araujo, ezio.melotti, georg.brandl, rhettinger, terry.reedy, tshepang
Priority: normal Keywords:

Created on 2012-02-11 21:11 by tshepang, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (3)
msg153138 - (view) Author: Tshepang Lekhonkhobe (tshepang) * Date: 2012-02-11 21:11
As an example, the date near the top of this document http://docs.python.org/py3k/whatsnew/3.0.html matches that of today, which can be misleading (it appears as if the thing was released today).

Also, by initial release, I mean the first "final", not the point release. Maybe any other date mentioned would perhaps be the date the docs were updated, *not* the date they were rebuilt.
msg153145 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2012-02-12 02:44
I agree that the date of the release would be more useful than the date of the doc build.
msg153156 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2012-02-12 03:51
I think this is the wrong place to show release dates (a subject that would be further confused by having multiple point releases).
History
Date User Action Args
2022-04-11 14:57:26adminsetgithub: 58204
2012-02-12 03:51:13rhettingersetstatus: open -> closed
resolution: rejected
messages: + msg153156
2012-02-12 02:44:35eric.araujosetnosy: + rhettinger
messages: + msg153145
2012-02-11 21:25:41ezio.melottisetnosy: + georg.brandl, terry.reedy, ezio.melotti, eric.araujo

versions: - Python 2.6, Python 3.1
2012-02-11 21:11:08tshepangcreate