On Oct 31, 5:38 am, mrts <[EMAIL PROTECTED]> wrote: > There has been much reluctancy in letting triagers tag and prioritize > 1.0.1 milestone tickets. Now that 1.0.1 is really close, can we > perhaps discuss what are the things that really should be fixed before > it is released? >
I have patches on a few tickets that have been bothersome: #9076 - Inline formsets without a default ordering and PostgreSQL backend can return a strange error when saving. This is somewhat related to #9006, though my patch avoids the problem of indexing into an unordered queryset entirely. From the CC list and comments, this has caused issues for quite a few people, though there is a workaround. #9308 - I originally re-opened #7778 because the fix for it unintentionally caused problems with my legacy database (foreign keys are not deferred). The new ticket describes the problem better, so I moved my patch over and closed #7778 again. The fix is simple and does not break the tests from #7778. On a somewhat related note, is there some reason that 1.0.1 and 1.1 milestones have not been created in Trac? It seems like triaging bugs into one of these releases should happen in Trac, not the mailing list. -bob --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
