[ python-Bugs-1476216 ] Documentation date stuck on "5th April 2006"
SourceForge.net
noreply at sourceforge.net
Thu Apr 27 14:26:11 CEST 2006
Bugs item #1476216, was opened at 2006-04-25 12:05
Message generated for change (Settings changed) made by akuchling
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1476216&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Mat Martineau (martineau)
Assigned to: Anthony Baxter (anthonybaxter)
Summary: Documentation date stuck on "5th April 2006"
Initial Comment:
My builds of the python documentation from the SVN
trunk have been stuck on "5th April 2006" for several
weeks now.
I've traced this to r43589, which hard-coded the date
in boilerplate.tex - this seems unusual, because
boilerplate.tex was not modified in this way for any
previous releases.
Seems like "\date{5th April 2006}" should be changed
back to "\date{\today}".
For some reason, the documentation at
http://docs.python.org/dev/ shows the correct date.
Mat
----------------------------------------------------------------------
>Comment By: A.M. Kuchling (akuchling)
Date: 2006-04-27 08:26
Message:
Logged In: YES
user_id=11375
Now that 2.5alpha2 is out, I've reverted boilerplate.tex to
use the current date.
----------------------------------------------------------------------
Comment By: A.M. Kuchling (akuchling)
Date: 2006-04-26 08:19
Message:
Logged In: YES
user_id=11375
This change was made for the 2.5alpha1 release. Undoing the
change probably just slipped the release manager's mind.
The freeze for alpha2 is very soon, so this will probably
get fixed after alpha2 is out.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1476216&group_id=5470
More information about the Python-bugs-list
mailing list