So you're aware of this, great! Sorry for mailing list noise then. On May 26, 1:32 pm, Russell Keith-Magee <russ...@keith-magee.com> wrote: > On Wed, May 26, 2010 at 8:22 AM, Mikhail Korobov <kmik...@googlemail.com> > wrote: > > 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 > > You're not the first person to notice this, and I agree that this is a > long time between releases. In our defense, the 1.1.X branch didn't > actually see much activity until very late in the 1.2 development > cycle (because the focus on new 1.2 features). If we had cut a 1.1.2 > in January, there actually wouldn't have been very much new in the > release -- in fact, unless the release was cut after January 28 > (r12344) there wouldn't have been anything especially compelling in > the 1.1.2 release -- it would have been a release mostly for the sake > of a release and bumping version numbers. > > That said, r12344 was a very important fix, and the long delay in > releasing 1.1.2 wasn't ideal. The delay was mostly caused by us being > overoptimistic about the time required for the final bug squashing > effort, and a lack of awareness about how important the r12344 bugfix > was until late in the process. We will try to do better handling this > sort of problem in the future. > > Yours > Russ Magee %-)
-- 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.
