Skip to content
Browse files

1.5 is no longer "UNDER DEVELOPMENT".

Thanks to Bruno Renie for reporting.
  • Loading branch information...
1 parent ab1c25f commit 481f3f13b54a5cacc5b67b32c4ada267fc709d21 @apollo13 apollo13 committed
Showing with 6 additions and 6 deletions.
  1. +3 −3 docs/releases/1.5-alpha-1.txt
  2. +3 −3 docs/releases/1.5.txt
View
6 docs/releases/1.5-alpha-1.txt
@@ -1,6 +1,6 @@
-============================================
-Django 1.5 release notes - UNDER DEVELOPMENT
-============================================
+==============================
+Django 1.5 alpha release notes
+==============================
October 25, 2012.
View
6 docs/releases/1.5.txt
@@ -1,6 +1,6 @@
-============================================
-Django 1.5 release notes - UNDER DEVELOPMENT
-============================================
+========================
+Django 1.5 release notes
+========================
Welcome to Django 1.5!

3 comments on commit 481f3f1

@mjtamlyn
Django member

:+1:

@carljm
Django member

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.

@apollo13
Django member

@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…

Please sign in to comment.
Something went wrong with that request. Please try again.