Re: Django 1.6 release timeline

Hey guys! Any updates? -- 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

Re: Django 1.6 release timeline

On Sun, Oct 6, 2013 at 4:31 AM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > Several release blockers were discovered over the last two weeks. > > Most were fixed, two are still open: > https://code.djangoproject.com/ticket/21197 > https://code.djangoproject.com/ticket/21164 >

Re: Django 1.6 release timeline

Several release blockers were discovered over the last two weeks. Most were fixed, two are still open: https://code.djangoproject.com/ticket/21197 https://code.djangoproject.com/ticket/21164 At this point the ETA for 1.6 RC1 is really "once these tickets are fixed". Thanks for your

Re: Django 1.6 release timeline

2013/9/26 seocam How are we going with the release process? Do we have a new date for the RC? > Well -- security issues got in the way :( and I'm still pondering over a release blocker: https://code.djangoproject.com/ticket/21134 Hopefully I'll deal with it during the

Re: Django 1.6 release timeline

Hi, How are we going with the release process? Do we have a new date for the RC? Cheers, -- Sergio Oliveira On Wednesday, September 11, 2013 3:42:33 PM UTC-3, Aymeric Augustin wrote: > > 2013/9/11 > >> Do you have an update on the schedule for the the Final? I guess it

Re: Django 1.6 release timeline

2013/9/11 > Do you have an update on the schedule for the the Final? I guess it would > be any week now, but I have some internal factors that require me to ask > for your updated forecast. > Hi Tony, Since we released 1.6 beta 3 yesterday, the next step is to release 1.6 RC

Re: Django 1.6 release timeline

Tim, Do you have an update on the schedule for the the Final? I guess it would be any week now, but I have some internal factors that require me to ask for your updated forecast. Thanks, Tony On Friday, August 16, 2013 7:14:48 AM UTC-7, Tim Graham wrote: > > Obviously, we've missed our

Re: Django 1.6 release timeline

Obviously, we've missed our target for the release candidate. We're currently targeting the week of August 26 for that, pending no new release blockers. You can help us make our goal by triaging unreviewed

Re: Django 1.6 release timeline

On Thu, May 2, 2013 at 4:42 AM, Aymeric Augustin wrote: > Shouldn't we push the alpha to May 23rd, all the more since we plan to fork > the stable/1.6.x branch at the beta? That sounds reasonable; give us a chance to get any work done at DjangoCon Europe into

Re: Django 1.6 release timeline

2013/5/2 Andrew Godwin > get something together for DjangoCon EU That's a good point. DjangoCon EU sprints are on May 18-19th. Shouldn't we push the alpha to May 23rd, all the more since we plan to fork the stable/1.6.x branch at the beta? -- Aymeric. -- You received

Re: Django 1.6 release timeline

PM, Carl Meyer <c...@oddbird.net> wrote: > Hi Shai, > > On 04/30/2013 04:38 PM, Shai Berger wrote: > > On Tuesday 30 April 2013, Jacob Kaplan-Moss wrote: > >> Hi folks - > >> > >> Unless there are strong objections, here's what I'm thinking for the &

Re: Django 1.6 release timeline

On 1 May 2013, at 00:35, Carl Meyer wrote: > On 04/30/2013 05:27 PM, Andrew Ingram wrote: >> Absolutely, there's no requirement to migrate, but it does have the >> feel of an weird kind of deprecation. Obviously there are >> workarounds, like you said, I can upgrade to 1.5

Re: Django 1.6 release timeline

Hi Shai, On 04/30/2013 04:38 PM, Shai Berger wrote: > On Tuesday 30 April 2013, Jacob Kaplan-Moss wrote: >> Hi folks - >> >> Unless there are strong objections, here's what I'm thinking for the >> Django 1.6 release timeline: >> >> Alpha: May 16 >>

Re: Django 1.6 release timeline

On 04/30/2013 05:27 PM, Andrew Ingram wrote: > Absolutely, there's no requirement to migrate, but it does have the > feel of an weird kind of deprecation. Obviously there are > workarounds, like you said, I can upgrade to 1.5 without changing > user models (though that does involve incurring a bit

Re: Django 1.6 release timeline

On 1 May 2013, at 00:13, Donald Stufft wrote: > > On Apr 30, 2013, at 7:10 PM, Andrew Ingram wrote: > >> On 30 Apr 2013, at 23:38, Shai Berger wrote: >>> I see one issue with this: According to current procedures, if this >>>

Re: Django 1.6 release timeline

On Apr 30, 2013, at 7:10 PM, Andrew Ingram wrote: > On 30 Apr 2013, at 23:38, Shai Berger wrote: >> I see one issue with this: According to current procedures, if this timeline >> is followed, support for 1.4 will be dropped less than 6 months after

Re: Django 1.6 release timeline

On 30 Apr 2013, at 23:38, Shai Berger wrote: > I see one issue with this: According to current procedures, if this timeline > is followed, support for 1.4 will be dropped less than 6 months after the > release of 1.5. At least for some of us (which, as I mentioned earlier on

Re: Django 1.6 release timeline

On Tuesday 30 April 2013, Jacob Kaplan-Moss wrote: > Hi folks - > > Unless there are strong objections, here's what I'm thinking for the > Django 1.6 release timeline: > > Alpha: May 16 > Beta: June 20 > RC: Aug 1 > Final: as early as Aug 8, or later if more RCs are

Re: Django 1.6 release timeline

On Apr 30, 2013, at 3:31 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > Hi folks - > > Unless there are strong objections, here's what I'm thinking for the > Django 1.6 release timeline: > > Alpha: May 16 > Beta: June 20 > RC: Aug 1 > Final: as ear

Django 1.6 release timeline

Hi folks - Unless there are strong objections, here's what I'm thinking for the Django 1.6 release timeline: Alpha: May 16 Beta: June 20 RC: Aug 1 Final: as early as Aug 8, or later if more RCs are needed. Remember that Alpha is the deadline for "big" features, so if you've got