On Mon, Apr 21, 2014 at 11:35 PM, Andrew Godwin wrote:
> Yes, no matter what it's too late to add anything to 1.7, which is a
> massive shame - we'll have to just heavily document this for now, and then
> investigate the dump/load data stuff for the next cycle (I think it should
> work everywhere
Today we've issued releases to remedy three security issues reported to us.
Affected versions are Django 1.4, Django 1.5, Django 1.6 and the Django 1.7
beta.
Full details and download information are on the Django project weblog:
https://www.djangoproject.com/weblog/2014/apr/21/security/
--
Yo
Yes, the test suite is basically the biggest obstacle to full usage of
migrations - I've tried to make it see sense, but given my limited time at
the moment and the fact that it's a tortuous mess of hacks in places it
means that I can't see that happening before the RC.
I'd like to have started th
I have been thinking that maybe we should delay #22340 (Legacy Table
Creation Methods Not Properly Deprecated) until 1.8 so that migrations
won't be required until Django 2.0. I'm not sure how feasible it is to
remove Django's test suite usage of it in the next week and a half, if we
are still
Are you thinking the next cycle would be 1.7.1 or 1.8?
On Mon, Apr 21, 2014 at 11:35 AM, Andrew Godwin wrote:
> Yes, no matter what it's too late to add anything to 1.7, which is a
> massive shame - we'll have to just heavily document this for now, and then
> investigate the dump/load data stuf
Yes, no matter what it's too late to add anything to 1.7, which is a
massive shame - we'll have to just heavily document this for now, and then
investigate the dump/load data stuff for the next cycle (I think it should
work everywhere initial_data did, at least, as they're both fixtures).
I will t
