Hello,
On 8 mai 2015, at 17:54, Carl Meyer wrote:
>
> On 05/07/2015 10:20 PM, Tai Lee wrote:
>> This sounds good. But will it significantly slow down the rollout of new
>> features into Django that require deprecation?
>
> No, because it would only delay the removal of deprecated features, not
Hi Tom,
When you say "testing migrations", what do you mean exactly? The migration
framework itself is heavily unit-tested, so I presume you intend to test
things like custom RunPython function bodies and the like?
Andrew
On Thu, May 7, 2015 at 3:30 AM, Tom Linford wrote:
> At Robinhood, we've
Hi Tim,
On 05/08/2015 08:28 AM, Tim Graham wrote:
> Do we need to make it easy to support two LTS releases at once? For
> example, at this point in time I expect projects to drop 1.4 support
> when adding 1.8 support, not try to support both given that 1.4 will be
> EOL in < 6 months. Assuming the
Hi Tai,
On 05/07/2015 10:20 PM, Tai Lee wrote:
> This sounds good. But will it significantly slow down the rollout of new
> features into Django that require deprecation?
No, because it would only delay the removal of deprecated features, not
prevent the initial deprecation. The only cost here is
Do we need to make it easy to support two LTS releases at once? For
example, at this point in time I expect projects to drop 1.4 support when
adding 1.8 support, not try to support both given that 1.4 will be EOL in <
6 months. Assuming the answer is no, practically, it might mean keeping
aroun
