I guess I noticed it updated the worst way possible:
- A commit has been pushed
- Continuous Integration tests passes
- CI sends "it's safe to deploy" signal to production server
- Downtime in production
My mistake? My "requirements.txt" file did not mention package versions.
Seeing the changelog, a lot of stuff changed. Seeing the tracebacks, some
helper applications I use ("django-avatar" is one of them) will need
updates before I migrate to the newer version.
Em sábado, 2 de dezembro de 2017 14:28:59 UTC-2, Tim Graham escreveu:
>
> Django 2.0 is now available:
>
> https://www.djangoproject.com/weblog/2017/dec/02/django-20-released/
>
> With the release of Django 2.0, Django 1.11 has reached the end of
> mainstream support. The final minor bug fix release (1.11.8) was
> issued today. As a long-term support release, Django 1.11 will receive
> security and data loss fixes until April 2020.
>
> Django 1.10 has reached the end of extended support. All Django 1.10
> users are encouraged to upgrade to Django 1.11 or later 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
>
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/e83f76b4-ee64-4b38-8e6e-1c5243228419%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
