Hi all, As I just noted on a blog entry, I've tagged the 1.3 release blocking bugs in Trac:
http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&keywords=%7Eblocker Most of these are fairly minor issues. However, there are 5 tickets that are regressions from 1.2.3 to 1.2.4: * #14880 - raw_id_fields failing in admin when used with limit_choices_to * #14947 - a test failure uner Python 2.7, only visible in 1.2.4 * #14975 - a test in contrib.auth causing *all* TransactionTestCases to fail in user code * #14982 - EMPTY_CHANGELIST_VIEW not being honored in list_display; again, in admin. * #14948 - A problem with multidb routers with m2m fields There is also one problem with the security patch itself: * #14999 - A problem with the security patch not allowing queries on local fields. This last ticket has been fixed in 1.2.X, but is obviously in the wild. 1.1.X is also affected, but I haven't backported to 1.1.X. We will obviously to do a 1.2.5 release when we hit 1.3 final; but I'm not sure if we should push an 1.2.5 (and 1.1.4) ASAP addressing these regressions, and then do 1.2.6 when we cut 1.3 final. This also points out that we should perhaps reconsider our release policy. Putting out security releases that include unrelated fixes is a bit of a risk. We've been bitten by this in the past, but never this bad. I would suggest that when security issues arises in 1.2.3, we should be releaseing 1.2.3.1 rather than 1.2.4. If a security release coincides with a point release -- as it did when we released 1.3beta1 -- we should release 1.2.3.1 (to address the security issue) *and* 1.2.4 (to get the other bugfixes). This will ensure that it is possible to update production code and get just the security fix, without any risk of regressions. Any opinions on these two points? 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.
