Re: [ANNOUNCE] Django 1.6 release candidate available
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 message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CANE-7mXEmxM2Y9qhBdz-zfyxH6gzWR%3DmUSfWvayuhMyfLB-dkA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [ANNOUNCE] Django 1.6 release candidate available
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 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 message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CANE-7mXEmxM2Y9qhBdz-zfyxH6gzWR%3DmUSfWvayuhMyfLB-dkA%40mail.gmail.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > -- Elyézer Rezende http://elyezer.com -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFsoaZvvt4Ah5_mdiXMHspJF5gf%3DK3bs33FmEGvNaw%3De-y74cA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [ANNOUNCE] Django 1.6 release candidate available
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 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 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 message because you are subscribed to the Google Groups >> "Django developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To post to this group, send email to django-developers@googlegroups.com. >> Visit this group at http://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/CANE-7mXEmxM2Y9qhBdz-zfyxH6gzWR%3DmUSfWvayuhMyfLB-dkA%40mail.gmail.com >> . >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Elyézer Rezende > http://elyezer.com > -- Elyézer Rezende http://elyezer.com -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFsoaZtDXeoxoCxiMZMY_WokBitT4%2BPVJ-p74PwtR4FNSY%3D13Q%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [ANNOUNCE] Django 1.6 release candidate available
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. > > 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 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 message because you are subscribed to the Google Groups >> "Django developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To post to this group, send email to django-developers@googlegroups.com. >> Visit this group at http://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/CANE-7mXEmxM2Y9qhBdz-zfyxH6gzWR%3DmUSfWvayuhMyfLB-dkA%40mail.gmail.com >> . >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Elyézer Rezende > http://elyezer.com > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAFsoaZvvt4Ah5_mdiXMHspJF5gf%3DK3bs33FmEGvNaw%3De-y74cA%40mail.gmail.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMwjO1Hh3zYDEGpmBTPz1avF8T57BRsFx%3DY%3DfOt6oXJvPtcRZg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [ANNOUNCE] Django 1.6 release candidate available
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 you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFsoaZvkkKuGP9KUVsgb%3Dx1yD1548_GzHf4T2x8HnFq0cAhSNg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
How do features get decided for a release?
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 community wants? Is there another way that developers get what the community wants? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/b4759c89-e99d-4928-8a22-7694ef903de0%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: How do features get decided for a release?
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 October 2013 13:45, 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? > I don't believe there's a specific roadmap for features. If someone writes a patch, it has a great chance to make it in. It's as simple as that (or, can be). > Is there a minimum time between releases? > >From the link above: "Minor release (1.1, 1.2, etc.) will happen roughly every nine months" > > Is there a minimum quota for fixed bugs for a release? > Critical bugs [such as data loss or crashes] and security fixes will warrant rapid release of a Micro version. Between Minor versions, they can vary a lot. > Is there ever a poll to see which features the community wants? > See the section "Phase one: feature proposal" Typically, a feature/ticket with code has a great chance to make it it. That said, a number of my changes that have made it into 1.7 were proposed and accepted in a matter of a few days. > Is there another way that developers get what the community wants? > Open a ticket, provoke discussion on the django-dev mailing list, and champion the ticket -- either by writing the code yourself, or finding someone to do it for you. As the release cycle notes say "working code trumps grand design" -- Curtis -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAG_XiSB4fj_LbqfG%3D2WcBCOV4sd_78a9RwX-fNTHt1TMQ4ddUQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: How do features get decided for a release?
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 bugs for a release? > > Is there ever a poll to see which features the community wants? > > Is there another way that developers get what the community wants? > Hi Cody, Django development -- like most open source development -- doesn't happen in the same way as commercial development. We don't sit down, decide features that we want, develop a plan, track progress against that plan, and deliver those features. We're an entirely volunteer driven organisation, and the thing about volunteers is that you don't have any carrots or sticks to drive the development process. I can't compel anyone to work on anything -- and if I punish people for not meeting my expectations, I'll probably find that my volunteers go away pretty quickly. Open source development means you have to recalibrate your thinking around how software gets developed. There isn't a minimum time between releases. We put out releases when we need to. We've historically put out point releases on a roughly annual timeframe, because that's matched our rate of development (and takes into account how much ; however, the 1.6 release is on track to be a 7 month development process. There isn't a minimum quota of bugs. The bugs that get fixed are the bugs that people provide patches for, and the core team can find sufficient time to review and commit. There isn't any sort of formal process for deciding what will be added. The features that are added are the features that volunteers feel sufficiently motivated to drive through the development process. Sometimes this means that features stay on the todo list for a long time, and sometimes it means that a feature goes from concept to completion in a matter of weeks. In essence, the community is getting *exactly* what it wants… in the sense that anyone who wants something bad enough is able to put in the time to develop a feature, and will drive it to completion. So - to answer the specific question -- Django 1.6 is about to be released (we just pushed our release candidate, which means the final is a matter of a week or so away). Django 1.7 is currently in feature development. The only features we can guarantee will be in Django 1.7 are those that we've already committed (most notably, migrations, and a couple of others that are listed in the release notes). I can take a guess at a couple of others that are *likely*, based purely upon the work that I myself am doing, and what I've heard other core team members talking about. However, until any of that code is committed, it's all speculative. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq84-agEjQE35sUUyj%3D4WKAnBbovaJKG8Ag6V35%2B%3DAdMBQBQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Model field metaclass magic (or lack thereof)
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/#modelforms-and-custom-fields I had a look though the tickets, but was unable to find any discussion on this. Is there a rationalé for not using this? Matt. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/21d71a45-f9d6-41bb-bba9-fce0a35b41ae%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Model field metaclass magic (or lack thereof)
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 > https://docs.djangoproject.com/en/dev/howto/custom-model-fields/#modelforms-and-custom-fields > > I had a look though the tickets, but was unable to find any discussion on > this. > > Is there a rationalé for not using this? > > Nothing specific that I'm aware of -- at a guess, I'd say it's an accident of history. DateField would have been one of the first fields written; generic tools for end-users to define their own field types would have come later. At that point, DateFields were a known entity with known behavior, so there wasn't any need to factor in the SubfieldBase functionality. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq848rerN71pcyk4yEkqeFO2zaAeVk8UfHZwpnz0zPw80HEg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
