1.5 is no longer "UNDER DEVELOPMENT".
Thanks to Bruno Renie for reporting.
This change still leaves the 1.5 release notes in master slightly out of sync with the version in the stable/1.5.x branch (i.e. the latter contains a date, there are probably other differences). This is a general problem we have, for instance I don't think the release notes for 1.3.6/1.3.7 exist anywhere except in the stable/1.3.x branch, and similar for 1.4.4/1.4.5. What is our policy on this? Should all release notes be forward-ported to master so that the master docs contain up-to-date versions of the release notes for every past release of Django? If that's what we want, then it'll require a more thorough fix.
@carljm I don't care too much, in the long run we probably should add release notes to the master branch and backport into the relevant release branch like we do with every other changeset…