On Mon, Apr 5, 2010 at 10:35 AM, Dennis Kaarsemaker <den...@kaarsemaker.net>wrote:
> Not a criticism per se, but I am wondering why the next 1.1.x is > released alongside 1.2 instead of as a release on its own. I've yet > again seen a case of python 2.6.5 breaking django tests, so I would > welcome a new release of 1.1.x a bit sooner than 1.2, if only from a > #django support perspective. > The problem is if we release Django 1.1.2 now, we still need another Django 1.1.X release simultaneously with 1.2 to package in an official release all remaining bug fixes backported to the 1.1.X branch before 1.2 is finalized. That would make for two very close together 1.1.X releases, which is generally not appreciated by users, though I realize it would be appreciated by early users of Python 2.6.5. Unfortunately the timing of Python 2.6.5 and Django 1.2 is a bit unfortunate here...for those who are quickly moving to Python 2.6.5 the best thing to do is run with a checkout of the 1.1.X branch. Karen -- 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.
