Re: Last call for 1.0 alpha

2008-07-21 Thread Jeremy Dunck
On Mon, Jul 21, 2008 at 10:49 AM, Marty Alchin <[EMAIL PROTECTED]> wrote: > I certainly hope 1.0 alpha isn't about hitting the > backwards-compatible limit yet, because if it is, #5361 has failed to > make the cut in time. The way I understand it, we still have some time > to introduce mild incomp

Re: Last call for 1.0 alpha

2008-07-21 Thread Karen Tracey
On Mon, Jul 21, 2008 at 12:57 PM, Chris Hasenpflug < [EMAIL PROTECTED]> wrote: > > I've opened #7867 for regressiontests.model_inheritance_regress > failures against MySQL. I've marked it 1.0 beta for now, but > depending on requirements of the test suite passing before tagging a > release. it ma

Re: Last call for 1.0 alpha

2008-07-21 Thread Tom Tobin
On Mon, Jul 21, 2008 at 10:18 AM, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > If there's anything that absolutely *MUST* be in 1.0 alpha, speak up > now. Please keep in mind that the alpha release is intended only for > the "must-have" features, which are now all in. This means that the > only

Re: Last call for 1.0 alpha

2008-07-21 Thread Chris Hasenpflug
I've opened #7867 for regressiontests.model_inheritance_regress failures against MySQL. I've marked it 1.0 beta for now, but depending on requirements of the test suite passing before tagging a release. it may need to reassigned. It looks like a mix-up of True/1 and False/0, but I havent really

Re: Last call for 1.0 alpha

2008-07-21 Thread Chris Hasenpflug
On Jul 21, 12:04 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > Are you saying these JUST started failing for MySQL?  This True/1 False/0 > issue has been known for a while (http://code.djangoproject.com/ticket/7190 > ). Wow...I'm on a roll today, lol. Somehow I didn't manage to find that one i

Re: Last call for 1.0 alpha

2008-07-21 Thread Marty Alchin
On Mon, Jul 21, 2008 at 11:37 AM, Tom Tobin <[EMAIL PROTECTED]> wrote: > Gah, I really haven't had time to do the > move-code-out-of-__init__-modules dance. I'm fairly certain that > it'll be completely backwards compatible (via re-importing back into > __init__), though, so I'm not too worried;

Re: Last call for 1.0 alpha

2008-07-21 Thread Jacob Kaplan-Moss
On Mon, Jul 21, 2008 at 8:48 AM, Gary Wilson Jr. <[EMAIL PROTECTED]> wrote: > I'm not at OSCON, but I can take care of #7864 (docs renaming), as I've > got a patch already in the works. Cool - go ahead and check that in; I'll give it a quick skim-over but doc fixes are easily done a bit after if

Re: Last call for 1.0 alpha

2008-07-21 Thread Jacob Kaplan-Moss
On Mon, Jul 21, 2008 at 8:48 AM, Karen Tracey <[EMAIL PROTECTED]> wrote: > I think it would be good if #7414 was fixed for alpha. Good call. I'm on 10.5 here so I can test it and get it done. Jacob --~--~-~--~~~---~--~~ You received this message because you are s

Re: Last call for 1.0 alpha

2008-07-21 Thread Gary Wilson Jr.
Jacob Kaplan-Moss wrote: > [If you happen to be at OSCON I'll be working on 1.0 alpha on the > lower floor over by the Starbucks if you wanna come over and help > out.] I'm not at OSCON, but I can take care of #7864 (docs renaming), as I've got a patch already in the works. Gary --~--~

Re: Last call for 1.0 alpha

2008-07-21 Thread Karen Tracey
On Mon, Jul 21, 2008 at 11:18 AM, Jacob Kaplan-Moss < [EMAIL PROTECTED]> wrote: > If there's anything that absolutely *MUST* be in 1.0 alpha, speak up > now. Please keep in mind that the alpha release is intended only for > the "must-have" features, which are now all in. This means that the > only

Last call for 1.0 alpha

2008-07-21 Thread Jacob Kaplan-Moss
Hi folks -- Well, with #285 fixed (thanks, Malcolm!) we're looking pretty good to release 1.0 alpha later today. Time-wise I think the plan is to do the release late this afternoon (CST), but that's really up to James. There's still a few tickets open in the 1.0 alpha milestone (http://code.djan