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
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
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
We've made the first release on the way to Django's next major release,
Django 1.10! With two and a half months until the scheduled final release,
we'll need timely testing from the community to ensure an on-time and
stable release. Check out the blog post:
https://www.djangoproject.com/weblog/
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
On Thu, May 19, 2016 at 02:56:48PM -0700, Quentin Fulsher wrote:
> Here is a super quick proof of concept that I put together. I just branched
> my fork of django and added a little to it. Here is the comparing changes
> page[1].
>
> Quick summary of changes: I created a dictionary that would co
