Re: Testing pre-release Django

The way we do it for Djangae right now is creating a `support-110` branch whenever we've got some capacity to start working on it, or we wanna assess the amount of work required. Here is a current status for our Django 1.10 support

Re: Testing pre-release Django

I've found testing your own projects on django master to be tremendously useful. Then, I don't have any surprise when I test on django alpha, everything passes and I have nothing to do. Not to mention the tremendous amount of things I learn on the way, at a slower, more regular pace. Compare this t

Re: Testing pre-release Django

> I'd be curious to hear from any third-party package maintainers how they feel about it. I've not found testing against master to be particularly helpful, as it's not apparent if an issue is substantial or not, without putting in work. The alpha releases *are* tremendously helpful for having a

Re: Testing pre-release Django

When contributing to apps (dependencies), I've noticed developers tend to expect a stable django release before merging in support and making a new stable release, rather than doing so before the new django release. This happened when I send patched to a few project with dj1.9 support. If the dja

Re: Testing pre-release Django

Please test your projects against django master too. On May 21, 2016 1:31 AM, "Ed Morley" wrote: > Another idea might be to encourage more packages to test on Travis against > Django master (with that sub-job marked as allowed to fail, so it doesn't > fail the whole run) - so any incompatibilitie

Re: Testing pre-release Django

Another idea might be to encourage more packages to test on Travis against Django master (with that sub-job marked as allowed to fail, so it doesn't fail the whole run) - so any incompatibilities become apparent earlier. eg: https://github.com/evansd/whitenoise/commit/c1a9f04cc90a7e48e536c651d9

Re: Testing pre-release Django

I'm completely supportive of this effort. In past release cycles, I've done testing with djangoproject.com and sent some PRs to its dependencies. The blocker to upgrading is always waiting for each project to make a release with the fixes. We could provide some guidance and suggest that project

Testing pre-release Django

Hi, I have the general feeling that too few people are testing the new Django major releases before the .0 release. The result being that many regressions are often reported after the release, while those could have been detected at alpha/beta/rc stages. I found myself in the situation where I