Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

1.5 is no longer "UNDER DEVELOPMENT".

Thanks to Bruno Renie for reporting.
  • Loading branch information...
commit 481f3f13b54a5cacc5b67b32c4ada267fc709d21 1 parent ab1c25f
Florian Apolloner authored February 28, 2013
6  docs/releases/1.5-alpha-1.txt
... ...
@@ -1,6 +1,6 @@
1  
-============================================
2  
-Django 1.5 release notes - UNDER DEVELOPMENT
3  
-============================================
  1
+==============================
  2
+Django 1.5 alpha release notes
  3
+==============================
4 4
 
5 5
 October 25, 2012.
6 6
 
6  docs/releases/1.5.txt
... ...
@@ -1,6 +1,6 @@
1  
-============================================
2  
-Django 1.5 release notes - UNDER DEVELOPMENT
3  
-============================================
  1
+========================
  2
+Django 1.5 release notes
  3
+========================
4 4
 
5 5
 Welcome to Django 1.5!
6 6
 

3 notes on commit 481f3f1

Marc Tamlyn
Owner

:+1:

Carl Meyer
Owner

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.

Florian Apolloner
Owner

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