Re: Last call for 1.0 alpha
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 incompatibilities in 1.0 beta, when it'll hit a hard > freeze. jacob, is this correct? >From the wiki VersionOneRoadmap: # There's a larger set of "maybe" features: if these features are done by the 1.0 feature-freeze date (August 5), they'll be included in 1.0. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Last call for 1.0 alpha
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 may need to reassigned. It looks like a mix-up of True/1 > and False/0, but I havent really looked at it in much depth. > 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 ). Karen --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Last call for 1.0 alpha
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 things that should hold up the release are serious blockers -- > things that would prevent substantial numbers of users from > successfully using Django. 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; I got a tad anxious about it a couple of weeks back, but I can't come up with a scenario that would break existing code. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Last call for 1.0 alpha
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 looked at it in much depth. And sorry about the mix-up on #7741...it was late and I realized the docs didn't get updated, so being a bit tired I decided to take the bath of least resistance :-) --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Last call for 1.0 alpha
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 in my searches. Thanks, Karen. I see that 7190 is not attached to a milestone. Where in the roadmap do we foresee "All tests passing" as a requirement? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Last call for 1.0 alpha
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; I got a tad anxious about > it a couple of weeks back, but I can't come up with a scenario that > would break existing code. 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 incompatibilities in 1.0 beta, when it'll hit a hard freeze. jacob, is this correct? -Gul --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Last call for 1.0 alpha
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 we need to. Jacob --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Last call for 1.0 alpha
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 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 -~--~~~~--~~--~--~---
Re: Last call for 1.0 alpha
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 --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Last call for 1.0 alpha
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 things that should hold up the release are serious blockers -- > things that would prevent substantial numbers of users from > successfully using Django. > I think it would be good if #7414 was fixed for alpha. The bug prevents correct install (data files are put in the wrong place) on OS X 10.5, and thus gives a bad first impression of Django, on what I think is a pretty important platform. It's got a patch, specific to that platform so it should be harmless on non-Macs. Getting it in sooner rather than later would help ensure this annoying issue that's cropped up a couple of times on different platforms is well and truly fixed with this patch for OS X. Karen --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Last call for 1.0 alpha
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.djangoproject.com/milestone/1.0%20alpha); I'm eyed them and they're all stuff that we indeed need to fix before we open the release. Of them, only #7825 has me really stumped, so if someone else can look at that and try to figure anything else, I'd be really grateful. 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 things that should hold up the release are serious blockers -- things that would prevent substantial numbers of users from successfully using Django. Jacob [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.] --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---