upgrade process.
>>
>> How about dropping all the shims in the release immediately following an
>> LTS? For example (slightly rewriting the past):
>>
>> 1.8 (LTS): No features dropped.
>> 1.9: Dropped features deprecated in 1.4, 1.5, 1.6, 1.7
>> 2.0: No f
;
> Feedback on that will would be welcome.
>
> On Wednesday, June 3, 2015 at 6:14:39 AM UTC-4, Philippe O. Wagner wrote:
>>
>> TLDR; Introducing django-compat - arteria's solution for for- and
>> backwards compatibility from Django 1.4.x to 1.8.x./1.9.x
>&
TLDR; Introducing django-compat - arteria's solution for for- and
backwards compatibility from Django 1.4.x to 1.8.x./1.9.x
SITUATION
We really love how Django evolves and how the core gets better and better.
New major versions of the framework that comes with changes, bugfixes and
new feat
