Re: 1.0.1 release blockers?

On Tue, Nov 11, 2008 at 5:02 AM, Daniel Roseman <[EMAIL PROTECTED]> wrote: > > Sorry to bring this discussion back to the original topic... > > http://code.djangoproject.com/ticket/9498 is a pretty serious > regression for us, which will prevent us upgrading to 1.0.1. There is > a patch, and I've

Re: 1.0.1 release blockers?

Sorry to bring this discussion back to the original topic... http://code.djangoproject.com/ticket/9498 is a pretty serious regression for us, which will prevent us upgrading to 1.0.1. There is a patch, and I've just added some tests - is there any chance this will make it into the release? Thank

Re: 1.0.1 release blockers?

On Nov 5, 2:31 pm, mrts <[EMAIL PROTECTED]> wrote: > little by a) milestones: assuring that there is a known date when a > given ticket will be looked at Let me clarify a little: "looked at" doesn't necessarily mean "integrated", it may be deferred to the next or a future milestone, i.e. it does

Re: 1.0.1 release blockers?

On Nov 5, 1:35 am, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On Tue, Nov 4, 2008 at 11:04 PM, mrts <[EMAIL PROTECTED]> wrote: > > > Most other projects are managed by a priority queue and clear target > > set for releases ("this has to go into 1.0.1, this can wait until > > 1.0.2"). No pr

Re: 1.0.1 release blockers?

On Tue, Nov 4, 2008 at 11:04 PM, mrts <[EMAIL PROTECTED]> wrote: > > Most other projects are managed by a priority queue and clear target > set for releases ("this has to go into 1.0.1, this can wait until > 1.0.2"). No problem if discussions on the mailing list are the > preferred way of doing it

Re: 1.0.1 release blockers?

On Tue, Nov 4, 2008 at 8:04 AM, mrts <[EMAIL PROTECTED]> wrote: > Except that most of the tickets that have been brought up in this > discussion already have patches, they just don't get the needed > attention from core devs. And if you feel that's the case, by all means bring them up. But there

Re: 1.0.1 release blockers?

On Nov 4, 2:33 am, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > Yes, there is a reason, and it has been given several times in recent > history. The v1.0.1 milestone has not bee created in Trac because it > will not in any way help us deliver the v1.0.1 release. There is no > difference betw

Re: 1.0.1 release blockers?

On Tue, Nov 4, 2008 at 2:58 AM, Bob <[EMAIL PROTECTED]> wrote: > 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. Yes, there is a

Re: 1.0.1 release blockers?

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 patche

Re: 1.0.1 release blockers?

On Oct 31, 5:19 pm, "Joey Wilhelm" <[EMAIL PROTECTED]> wrote: > I would like to suggest the following: > http://code.djangoproject.com/ticket/9245 > http://code.djangoproject.com/ticket/6710 > > They both have fully functional patches... although granted the second has > no tests. IMHO http://cod

Re: 1.0.1 release blockers?

I would like to nominate: http://code.djangoproject.com/ticket/8754 http://code.djangoproject.com/ticket/9206 Both have patches which still apply, and just haven't been reviewed yet. Richard. --~--~-~--~~~---~--~~ You received this message because you are subscri

Re: 1.0.1 release blockers?

On Sun, Nov 2, 2008 at 6:54 AM, Tai Lee <[EMAIL PROTECTED]> wrote: > I've put this ticket back to "accepted" as per your comment that the > bug should be fixed. As you say, the DDN and confused comments were > not intended to raise a red flag, and should have been taken to a > separate ticket. The

Re: 1.0.1 release blockers?

On Nov 2, 10:57 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > > You do know that Karen has a commit bit, right? If she's got concerns > about a ticket, then I at least take that as meaning it's got problems > and isn't ready for checkin. Yes, I did notice that. However, as I said, there is sti

Re: 1.0.1 release blockers?

On Sun, Nov 2, 2008 at 5:54 AM, Tai Lee <[EMAIL PROTECTED]> wrote: > There's still no comment in the ticket from a core developer or > anybody else, though. As this is a simple bug fix, can I (as the > reporter) mark this ready for checkin, as there is a patch with tests? You do know that Karen h

Re: 1.0.1 release blockers?

Thanks for your feedback, Karen. > http://code.djangoproject.com/ticket/8898 > > I suspect this one may be stalled because it is in design decision needed > state with a last comment that makes it sound like the existing patch (added > before the last comment) is not correct and that the right fi

Re: 1.0.1 release blockers?

On Sat, Nov 1, 2008 at 9:14 PM, Tai Lee <[EMAIL PROTECTED]> wrote: > > #8898 and #9482 are both simple bug fixes with patches that remain > unreviewed. #9214 is a simple backwards compatible enhancement with > patch. > > I'm reluctant to mark them "ready for checkin" as I am the reporter, > but it

Re: 1.0.1 release blockers?

On Nov 1, 1:38 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > > 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

Re: 1.0.1 release blockers?

Karen Tracey wrote: > On Fri, Oct 31, 2008 at 6: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 t

Re: 1.0.1 release blockers?

On Fri, Oct 31, 2008 at 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? We

Re: 1.0.1 release blockers?

I would like to suggest the following: http://code.djangoproject.com/ticket/9245 http://code.djangoproject.com/ticket/6710 They both have fully functional patches... although granted the second has no tests. --~--~-~--~~~---~--~~ You received this message because y

Re: 1.0.1 release blockers?

On Fri, Oct 31, 2008 at 6: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? >

Re: 1.0.1 release blockers?

Ahh whoops, I have a patch for that(only covers unique right now), will upload now. Alex On Oct 31, 9:26 am, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote: > On Fri, Oct 31, 2008 at 4:38 AM, mrts <[EMAIL PROTECTED]> wrote: > > The only major issue I have encountered > > ishttp://code.djangoproj

Re: 1.0.1 release blockers?

And whoops again, brosner has a patch that covers the parent fkey issue. My patch covers the issue of duplicate data within the formset. On Oct 31, 9:26 am, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote: > On Fri, Oct 31, 2008 at 4:38 AM, mrts <[EMAIL PROTECTED]> wrote: > > The only major issue

Re: 1.0.1 release blockers?

On Fri, Oct 31, 2008 at 4:38 AM, mrts <[EMAIL PROTECTED]> wrote: > The only major issue I have encountered is > http://code.djangoproject.com/ticket/8882 Thanks for the pointer; I'd agree this should get in. Jacob --~--~-~--~~~---~--~~ You received this message

1.0.1 release blockers?

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? The only major issue I have encountered is http://code.djangoproject.com/ti