Re: Django 2.0 released
I just wanted to take the chance to thank Tim and all the other people
working on Django, especially on this big milestone for the project.
At least for me It has served me well over the last 5 years, has
incorporated many useful features while still being relatively lean, and
has top notch documentation.
Thanks for the hard work guys!
On Sun, Dec 3, 2017 at 10:40 PM, Jorge Gimeno wrote:
> If you use pipenv, it will do that for you.
>
> -Jorge
>
> On Dec 3, 2017 3:05 PM, "Simon Charette" wrote:
>
>> > My mistake? My "requirements.txt" file did not mention package versions.
>>
>> You should definitely make sure to lock/freeze your requirements to
>> prevent
>> your application's behavior from changing under your feet.
>>
>> Best,
>> Simon
>>
>> Le samedi 2 décembre 2017 15:02:55 UTC-5, Adler Neves a écrit :
>>>
>>> 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/ms
>> gid/django-users/9d01a490-ded0-4d22-8d3b-6734968eaaf5%40googlegroups.com
>>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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/CANfN%3DK8uW-kK5YSkh0VA10%2B3aySezEwBa8--%2BUSetjri-
> aVn5w%40mail.gmail.com
>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
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/CALn3ei1rR%3D4FvVFwTi-RmMMtrOqj_e4vMdGwro8dtv-mnsAdOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: Django 2.0 released
If you use pipenv, it will do that for you.
-Jorge
On Dec 3, 2017 3:05 PM, "Simon Charette" wrote:
> > My mistake? My "requirements.txt" file did not mention package versions.
>
> You should definitely make sure to lock/freeze your requirements to prevent
> your application's behavior from changing under your feet.
>
> Best,
> Simon
>
> Le samedi 2 décembre 2017 15:02:55 UTC-5, Adler Neves a écrit :
>>
>> 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/9d01a490-ded0-4d22-8d3b-6734968eaaf5%40googlegroups.com
>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
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/CANfN%3DK8uW-kK5YSkh0VA10%2B3aySezEwBa8--%2BUSetjri-aVn5w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: Django 2.0 released
> My mistake? My "requirements.txt" file did not mention package versions.
You should definitely make sure to lock/freeze your requirements to prevent
your application's behavior from changing under your feet.
Best,
Simon
Le samedi 2 décembre 2017 15:02:55 UTC-5, Adler Neves a écrit :
>
> 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/9d01a490-ded0-4d22-8d3b-6734968eaaf5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Django 2.0 released
That's a terrible way to find out about a new release. Hope you didn't
suffer too much!
Regards,
Andréas
2017-12-02 19:07 GMT+01:00 Adler Neves :
> 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.
>
--
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/CAK4qSCf2YBRjVWYmV6FerfGissG3qpnMZAYWPxe1qrTmQaaMgg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: Django 2.0 released
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.
Django 2.0 released
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/CAD-rxRAUEn6cHk_uMLd8fU7R6m_gAsT9xv85Pyf3mUPKJnzdvg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
