I want to raise the question about stable django micro-releases. 1.1 - July 2009, 1.1.1 - October 2009 (released because of security bug), 1.1.2 - May 2010
So if some abstract developer want to use stable django release and follow all the instructions in docs he can get the half-year outdated django with a number of known bugs that are already fixed in svn. Please also consider what happen with the csrf_token template tag: it is in 1.1.2 to ease the migration to 1.2 but 1.1.2 is released alongside with 1.2 and not before 1.2. The most logical time for 1.2- preparing 1.1.2 release could be a feature freeze for 1.2 (months before the 1.2 release). I think the releases of stable micro-releases should happen more often for 1.2. You guys are doing great job and it is not good to hide it from developers. This is also can be solved with a bit of documentation. If the release process is time-consuming and is a waste of developers' time then there is an another way: add the suggestion to use stable svn branch somewhere in docs. This may be obvious for somebody that there is a stable django branch in the svn but I'm sure there are a lot of developers who don't know this. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
