Re: Django 3.0 Released.

On that subject... 

On Thu, 5 Dec 2019, 15:12 Jonathan Morgan, <jonathan.morgan.007@gmail.com> wrote:

Another thing to consider is whether you need to update the packages you use to build your application.  I've found that support for the LTS version of django is not consistent across packages, where support for the latest version is much more consistent, such that sometimes a needed update to a package required me to update django, either because of the package itself only working on a newer version, or one of its dependencies having this constraint.  Because of this, I tend to keep my applications running on the latest django

This is generally our preference too. But it does depend on the related packages we use to stay compatible. I generally try to help here by trying out early copies against our test suite and reporting issues early. This time this approach worked for all but one related package (I have my fingers crossed for that one). 

, rather than an LTS, so I can also keep updating the related packages.  I also personally find the changes needed to move an application from version to version of django to be much more managable if you do it every version, in small chunks, rather than waiting between LTS versions, but your mileage and stomach for these updates may vary.

On Wednesday, December 4, 2019 at 1:48:06 PM UTC-5, Andréas Kühne wrote:

So your question is if you should use LTS versions or use the latest blazing version.

The answer is of course - it depends.

Do you see anything in django 3 that you need to have? In that case - upgrade to django 3. If you only want to make sure that your application is safe and secure and you don't need the bleeding edge functionality - keep with the LTS:es.

It also depends on your application cycle. I currently have 2 projects running - one is a commercial ecommerce platform. The other is a platform for course administration. Both have completely different requirements on technical functionality from django. On the ecommerce site we are running on LTS versions, on the other site we are running with the latest version of django.

I think the most important thing is to make sure that you have a secure site regardless - so if you run the lts versions, you need to update as soon as the next LTS comes out. And the same goes for the other versions as well - update all the time in that case.

Regards,

Andréas

Den mån 2 dec. 2019 kl 22:18 skrev o1bigtenor <o1big...@gmail.com>:

On Mon, Dec 2, 2019 at 6:18 AM Carlton Gibson <carlto...@gmail.com> wrote:
>
> Django 3.0 is now available.
>
> https://www.djangoproject.com/weblog/2019/dec/02/django-3-released/
>
> With the release of Django 3.0, Django 2.2 has reached the end of
> mainstream support. The final minor bug fix release (which is also a
> security release), 2.2.8, was issued today. Django 2.2 is an LTS release and
> will receive security and data loss fixes until April 2022. All users are
> encouraged to upgrade before then to continue receiving fixes for
> security issues.
>
> See the downloads page [1] for a table of supported versions and the
> future release schedule.
>
> [1] https://www.djangoproject.com/download/#supported-versions
>
Greetings

Thank you - - - -interesting news!

I'm a little confused though - - - - I have, at least in many things
so far that I've used,
software I mean, tended to move from one long term service version to the next.
Yet - - - Django is different - - - - it is suggested that I leave a
long term version
for a short term version, which will itself be followed by a short
term version, and then
after another period of time there will be a long term service
version. Shortly after
that long term service version has been reached, if the pattern used
for the transition
from version 2 to 3, version 4 will be offered.

So - - - - what gives the best long term stability of function for use
of Django?

1. forget long term service versions and expect to revise you code
every 6 to 8 months
2. use LTS code but using it until the release of the next major
version means that
      interesting advancements again mean a relentless pattern of revision
3. don't worry about LTS and write the code and get the application to
work well and
     hope that I can hold things working without major security issues
until its worth
     redoing the application.

I'm starting to think that option #3 is looking more attractive.

Regards

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAPpdf58DU9XPYM-FOJ1%3DSy-PObNDJ%2B2Xw8hk3sr9BxTdFYcDjg%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/63b2f084-85d7-412c-8a44-c09043c2a595%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAHAc2jeDZucGX2h56Z34usgi4-bMJpaf9dZxLu%3D_Er4jXk4mFw%40mail.gmail.com.