Re: [ANNOUNCE] Django 1.6 release candidate available

2013-10-23 Thread Aymeric Augustin
2013/10/23 Yishai Beeri > Small discrepancy: the blog post states python 2.7 is required; the > release notes it links to state python 2.6.5 is still supported, and 2.7 > will be required from Django 1.7 onwards. I've updated the blog post. Thank you. -- Aymeric. -- You received this messag

Re: [ANNOUNCE] Django 1.6 release candidate available

2013-10-23 Thread Elyézer Rezende
I think I have missed something or migrations will not be part of this release? I have not found it on release notes. Thanks On Wed, Oct 23, 2013 at 5:03 AM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > 2013/10/23 Yishai Beeri > >> Small discrepancy: the blog post states py

Re: [ANNOUNCE] Django 1.6 release candidate available

2013-10-23 Thread Elyézer Rezende
I have found the answer in the migrations docs [1], there says that will be 1.7. Sorry [1] https://docs.djangoproject.com/en/dev/topics/migrations/ On Wed, Oct 23, 2013 at 10:56 AM, Elyézer Rezende wrote: > I think I have missed something or migrations will not be part of this > release? > > I

Re: [ANNOUNCE] Django 1.6 release candidate available

2013-10-23 Thread Marc Tamlyn
Migrations landed after the feature freeze for the beta and are not quite feature complete yet. They will be part of 1.7. On 23 Oct 2013 13:57, "Elyézer Rezende" wrote: > I think I have missed something or migrations will not be part of this > release? > > I have not found it on release notes. >

Re: [ANNOUNCE] Django 1.6 release candidate available

2013-10-23 Thread Elyézer Rezende
On Wed, Oct 23, 2013 at 10:58 AM, Marc Tamlyn wrote: > Migrations landed after the feature freeze for the beta and are not quite > feature complete yet. They will be part of 1.7. > Thank you Mark, this clarify it more. -- Elyézer Rezende http://elyezer.com -- You received this message because

How do features get decided for a release?

2013-10-23 Thread Cody Scott
I know that I can look at the 1.7 release notes to see what is to come in the next release. How do django developers decide what features to work on? Is there a minimum time between releases? Is there a minimum quota for fixed bugs for a release? Is there ever a poll to see which features the

Re: How do features get decided for a release?

2013-10-23 Thread Curtis Maloney
Hi Cody, I suspect many of your questions may be answered in the documentation here: https://docs.djangoproject.com/en/1.5/internals/release-process/ Here's some comments from my experience with using django since its initial release, and recently making a concerted effort to submit code. On 24

Re: How do features get decided for a release?

2013-10-23 Thread Russell Keith-Magee
On Thu, Oct 24, 2013 at 10:45 AM, Cody Scott wrote: > I know that I can look at the 1.7 release notes to see what is to come in > the next release. > > How do django developers decide what features to work on? > > Is there a minimum time between releases? > > Is there a minimum quota for fixed bug

Model field metaclass magic (or lack thereof)

2013-10-23 Thread schinckel
Hi, I was wondering if there was any reason why fields such as models.DateField() do not use the SubFieldBase metaclass trick to ensure they always contain instances of the correct class? I'm referring to the description from https://docs.djangoproject.com/en/dev/howto/custom-model-fields/#mode

Re: Model field metaclass magic (or lack thereof)

2013-10-23 Thread Russell Keith-Magee
On Thu, Oct 24, 2013 at 12:08 PM, schinckel wrote: > Hi, > > I was wondering if there was any reason why fields such as > models.DateField() do not use the SubFieldBase metaclass > trick to ensure they always contain instances of the correct > class? > > I'm referring to the description from > ht