Re: How do features get decided for a release?

2013-10-24 Thread Marc Tamlyn
That's to do with the date a feature lands. Migrations isn't completely feature complete or totally stable yet - squashing migrations actually landed in the master branch this week. When we release the beta, the version goes into feature freeze so only minor bug fixes and any critical issues get

Re: How do features get decided for a release?

2013-10-24 Thread Cody Scott
How do you decide which version to put a feature in? Why wasn't migrations in 1.6? On Thu, Oct 24, 2013 at 12:01 AM, Russell Keith-Magee < russ...@keith-magee.com> wrote: > > On Thu, Oct 24, 2013 at 10:45 AM, Cody Scott wrote: > >> I know that I can look at the 1.7

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

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

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