On Tue, Nov 29, 2011 at 6:10 AM, Luke Plant <l.plant...@cantab.net> wrote: > On 28/11/11 20:33, Adrian Holovaty wrote: >> I plan on starting this next week. Is there a list somewhere of what >> needs to get done? If not, I can make it, but obviously it'd be great >> if that already existed. > > 1) Release blockers: > > https://code.djangoproject.com/query?status=!closed&severity=Release+blocker&order=priority
I took care of four of those blockers today: Autoescaping variable input in template tags https://code.djangoproject.com/ticket/10912 Select Filter (its "to" box) has 0 height if in a collapsed fieldset https://code.djangoproject.com/ticket/17218 Admin should hide password hash field by default https://code.djangoproject.com/ticket/16845 Regression introduced by r16739 -- `ManyRelatedManager.add()` doesn't commit to database https://code.djangoproject.com/ticket/16818 We have six remaining blockers. Here's the status (from my perspective) on the ones I looked at: _destroy_test_db exposes the production database to possibly destructive actions from the unit tests https://code.djangoproject.com/ticket/10868 STATUS: Waiting for a patch. Improved Auth Password Hashing https://code.djangoproject.com/ticket/15367 STATUS: Didn't get a chance to play with the patch/branch yet, but it sounds promising from the comments. I'm happy to help write documentation on it (which is one of the remaining issues). https://code.djangoproject.com/ticket/16563 STATUS: This is a weird one, and I'm not sure what the best solution is. It would benefit from some more eyes. The other three, I haven't looked at yet... Adrian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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.
