On 9/16/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > s/would/will/ -- I'm gonna try to have this wrapped up in the next couple > days.
Cool. I've paused for a bit of a break, but here's some info on what I've been doing. My process today has been to simply go to the big list of open tickets and read them, one by one. This has been slow and painful, but mostly because we don't do that often enough :) Right now I'm up to #5002, which means I'm in the home stretch; my methodology has been: 1. For issues which have spawned out multiple tickets, pick a "master" ticket and dupe the rest, with references from the master back to any relevant discussion or patches. 2. For tickets which have been sitting at "design decision needed" with no activity for an excessively long period of time (more than a year in several cases), wontfix with a comment inviting anyone who wants to champion it to pick it up and make a case. 3. For tickets which will be obsoleted by newforms-admin, add a note saying so. For some very specific (and usually old) customization requests, I've closed the ticket as well. 4. For things which I can verify have been fixed in other commits, close fixed with a note explaining the feature, fix or -- if I could find it -- changeset which fixed them. 5. Anything related to JavaScript or CSS in the admin got assigned to Christian, who's going to wish he never volunteered to help with that ;) A couple of "master tickets" to note: * Everything related to customizing FileField is being duped and pointed at #5361. * Everything related to easier ways to automatically and/or manually add CSS classes or other HTML fanciness to newforms fields/widgets is being duped and pointed at #3515. * Everything which would be solved by a cleaner solution for app_label is being duped and pointed at #3591. Two things which don't have obvious "master" tickets but need them: 1. Initial SQL parsing problems. There are a *lot* of these. 2. Weird issues created by "primary_key=True". 3. Weird issues created by "to_field". I'm waffling between #4088 and #4306, and may arbitrarily choose one. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
