1.7 release?

[Stephen Burrows]

It's been a while since I've heard anything about the 1.7 release - but it looks like there aren't any release blockers left. And there weren't any the last time I checked either. What's the status? Is it just waiting for final review? Is it just waiting for DjangoCon? Is there anything that community members can do?

[Florian Apolloner]

On Tuesday, August 19, 2014 10:01:22 AM UTC+2, Stephen Burrows wrote:

What's the status?

Good so far, release will be there soon (tm).

Is there anything that community members can do?

Yes, test it heavily -- especially migrations :)

[Florian Apolloner]

On Tuesday, August 19, 2014 10:01:22 AM UTC+2, Stephen Burrows wrote:

Is there anything that community members can do?

Oh, and reviewing unreviewed  tickets, so we can make sure there are no new release blockers.

Cheers,
Florian

[Collin Anderson]

I'm not a core developer, but here's the current situation as far as I can tell.

There's been a steady stream of about releases blocker coming in almost once per day, most of them migrations related:

https://code.djangoproject.com/query?version=!master&resolution=fixed&severity=Release+blocker&or&status=assigned&status=new&version=!master&severity=Release+blocker&col=id&col=summary&col=version&col=status&col=time&col=changetime&desc=1&order=id

So my guess is: once it feels like there aren't any more release blockers coming in (maybe a few days without a release blocker), the next step will likely be to put out another release candidate. In order to put out the final 1.7 release, this release candidate would need to be out and have few major bugs for at least two weeks, otherwise we'd need to do yet another release candidate.

So, like Florian said, the more we can test the latest 1.7.x code especially migrations, the sooner we can discover and fix the major bugs.

[Andrew Godwin]

Collin is correct. Basically, as soon as there's 2 or 3 days without a release blocker, we'll roll an RC3, and then hopefully there'll be no more blockers filed and we can do a final release.

At this point, we're still a few weeks away from a final release at best.  The release itself is pretty stable; the problem is that migrations are so complicated and provide such a large new feature surface that people are finding "crash bugs" (i.e. where you give Django some set of inputs and it crashes during migrations) every day or two with increasingly complex sets of apps. These are the sorts of things I would have released South with and fixed in a later release, but we hold Django to a higher standard.

Andrew

--
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-develop...@googlegroups.com.
To post to this group, send email to django-d...@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/9fdbbd92-cc07-4f22-9a89-e394566d03d8%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Ryan Hiebert]

> On Aug 19, 2014, at 12:02 PM, Andrew Godwin <and...@aeracode.org> wrote:
>
> At this point, we're still a few weeks away from a final release at best. The release itself is pretty stable; the problem is that migrations are so complicated and provide such a large new feature surface that people are finding "crash bugs" (i.e. where you give Django some set of inputs and it crashes during migrations) every day or two with increasingly complex sets of apps. These are the sorts of things I would have released South with and fixed in a later release, but we hold Django to a higher standard.

While I’m very impatient to get 1.7, I’m also very grateful that you guys take the time to build and test a release so that it is solid. Thank you.