Tim, Yes I see. This is great. I agree with your assessments in full.
On 10/31/2014 06:19 PM, Tim Graham wrote: > Hi Justin, > > Thanks for the feedback. Making 1.8 the next LTS was discussed a bit > internally before I shared the idea and tentative schedule for the 1.8 > release on the thread "1.8 release planning." The only feedback on > that thread (2 weeks ago) was from Josh Smeaton who supported the > details outlined there. There is still time to weigh in there if you like. > > Tim > > On Friday, October 31, 2014 8:28:26 PM UTC-4, Justin Holmes wrote: > > Tim, > > This truly is a stellar report. Thanks so much. > > I do have one question about this statement: > > > A reminder that we expect Django 1.8 to become the next LTS > version of > Django, so if you have a pet bug or feature, now's a great time to > get > it fixed! > > You characterize this as a "reminder" - I didn't realize this had > been > firmly decided, although it was obviously discussed at DjangoCon. > Although I'm definitely in support, I am curious: who made this > decision > and when? > > > On 10/31/2014 04:04 PM, Tim Graham wrote: > > > > To briefly summarize the triage and review work, we continue to > > retrieve good bug reports for Django 1.7, particularly migration > edge > > cases. I'd expect to see another bug fix release for the 1.7 series > > within a month of 1.7.1. One issue the core team will be > addressing at > > the "Django: Under the Hood" conference in mid-November is > adding more > > team members to the list of people who can release Django. The > lack of > > availability of someone who has the time and privileges to do a > > release has been a bottleneck on occasion. In addition to bug > fixing > > on the 1.7 branch, master (1.8) continues to receive a steady > diet of > > new small features. A reminder that we expect Django 1.8 to > become the > > next LTS version of Django, so if you have a pet bug or feature, > now's > > a great time to get it fixed! > > -- > You received this message because you are subscribed to the Google > Groups "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to django-developers+unsubscr...@googlegroups.com > <mailto:django-developers+unsubscr...@googlegroups.com>. > To post to this group, send email to > django-developers@googlegroups.com > <mailto:django-developers@googlegroups.com>. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/98ff9e20-5bc9-474a-aef0-538b1b479aa7%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/98ff9e20-5bc9-474a-aef0-538b1b479aa7%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/54543B54.1080004%40gmail.com. For more options, visit https://groups.google.com/d/optout.
