On Wed, Dec 15, 2010 at 3:29 PM, Shai Berger <[email protected]> wrote: > Hi, > > On Tuesday 14 December 2010, Russell Keith-Magee wrote: >> >> From an initial inspection, none of these tickets are subject to the >> feature freeze, because none of them are features. They're all bugs >> (which are fair game until the RC) or documentation updates (which are >> fair game right up until the final release). >> > What about http://code.djangoproject.com/ticket/9964 ? > > It's a bug, but the suggested fix includes behavior change and possibly even a > backward-incompatible change. > > Does the feature freeze apply?
The feature freeze only ever applies to *features*. In the case of #9964, there is no new feature, it's a correction to existing behavior. As I noted last time you raised this ticket, the only question is whether this is genuinely a bug, or a behavioral misfeature that needs correcting. If it's a bug, then no backwards compatibility issue exists, because bugs aren't covered by our backwards compatibility policy. FYI - I had a quick look at #9964 during the recent Sydney sprint, but not enough to push the ticket forward or commit it; I was intending to give #9964 a solid look once the feature freeze happens. 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
