Philippe
>>> >
>>> > Am Mittwoch, 3. Juni 2015 15:25:21 UTC+2 schrieb Tim Graham:
>>> > When do you drop support for old versions of Django? The main concern
>>> I have is that it somewhat encourages running on unsupported and insecure
>>> v
urrently 1.5, 1.6; and 1.4 will be end of life in
>> October). Therefore I don't thinking giving it an official blessing is a
>> good idea.
>> >
>> > In the "1.9 release planning" thread I proposed a new deprecation
>> schedule to make it eas
le to make it easier for third-party apps to support the currently
> supported Django versions now that we have LTS releases. Here's that
> proposal:
> >
> >
> https://docs.google.com/document/d/1bC6A8qc4skCmlagOnp8U7ddgyC-1XxXCBTlgrW690i0/edit?usp=sharing
>
ty apps to support the currently supported Django
> versions now that we have LTS releases. Here's that proposal:
>
> https://docs.google.com/document/d/1bC6A8qc4skCmlagOnp8U7ddgyC-1XxXCBTlgrW690i0/edit?usp=sharing
>
> Feedback on that will would be welcome.
>
> On Wednesday, J
;
> 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
>&
c4skCmlagOnp8U7ddgyC-1XxXCBTlgrW690i0/edit?usp=sharing
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.
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
