Excellent, I hope you guys get many hours for coding! Here's a few comments based on my triage experience (whatever that's worth):
My vote would be for spending some time on edit_inline (e.g. http://code.djangoproject.com/wiki/FeatureGrouping#Multipleedit_inlineissues), as this alone is causing craploads of bugs and cleaning all these out would be great. AFAIK, Malcolm was looking into this after his rewrite of the query code, but I don't know if he's made any progress. I think the next major issue is the unicodisation problems - it may be a good idea while you're all together to sit down and plan what's going to happen (post 0.96) as I think the newforms will start exposing problems here (See the FeatureGrouping page for a list) - is Unicodisation going to be a 1.0 feature for a start? Third, there are lots of translation tickets ready for checkin, which would be nice to patch in. Django's got a good reputation for i18n/ l10n, so getting these into 0.96 would be good. This would also give translators a chance to find and clean up any final glitches before 1.0 Finally, it may be a good time to glance over all the "Design Decision Needed" tickets, with most of you core dev's there, it should be an easy yes/no process for most of them. Cheers, & have a good one guys. -Simon G. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
