Karen Tracey wrote: > On Fri, Oct 31, 2008 at 6:38 AM, mrts <[EMAIL PROTECTED] > <mailto:[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? > > > Really, there is not reluctance to get input on what should be fixed > before 1.0.1 is released. It's just that input in the form of working > patches with tests and doc is far more valuable than a simple bit on a > ticket. The list of tickets that are ready for checkin is not so big > (and some of them are enhancements so not candidates for 1.0.1. > <http://1.0.1.>) that we need some other bit to say "look at this > before releasing 1.0.1". > > > The only major issue I have encountered is > http://code.djangoproject.com/ticket/8882 > that makes inline formsets that have unique fields (that is, pretty > much every other use case for them) unusable. Looks like brosner is > already working on it -- thanks! -- and it would be perhaps wasteful > if 1.0.1 is released before he has finished. > > > It really depends on how close a fix is as to whether it would be > worthwhile holding up a bugfix release on any one ticket. I'm not > talking about this ticket in particular (which I haven't looked at and > it sounds like it's already on others' radars so likely will get in, > assuming it's not too terribly difficult to fix) -- I'm trying to get > across that holding up a bugfix release in hopes of a not-yet-existent > fix for a bug that's already in a shipped release doesn't make much > sense, unless you've got some reason to believe a fix will be > appearing real soon now. There are already many bugs that have been > fixed in the 1.0.X branch and will benefit users. 1.0.1 will be > better than 1.0, and 1.0.1 released in the very near future with n-x > bugs fixed is better than 1.0.1 released at some unknown future data > with those those additional x bugs fixed. > Well right, that'll be 1.0.2 if it's needed. Though with 1.1 on the way it seems less than likely.
regards Steve --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
