Am 04.04.2015 14:30, schrieb Tim Graham:
Now that Django 1.8 is released, I wanted to bump this thread for
discussion so we can hopefully ratify this schedule or modify it based
on feedback. In particular, I heard a concern that a six month release
schedule may be too often for the community. On the other hand, I
think smaller releases would make incremental upgrades easier.
I started to use django years ago and I like it but these fast releases
result in quite some projects running django version not getting any
security fixes anymore, yes there is the LTS but if I start a new
project I use the current version to get features not being in the LTS
version and I dont have the time to upgrade all projects to the current
and do in depth testing if all works like expected and such a fast
release cycle makes it even worse, if there is such an fast release
cycle at least older version should get security fixes too otherwise its
kinda unattractive to use it.
One difficulty could be if third-party packages try to support every
version since the last LTS (this seemed to be common with 1.4). A 6
month release schedule would mean 5 versions of Django until the next
LTS, instead of 3 as we had since 1.4, so more `if DJANGO_X_Y`
conditionals. One idea is that third-party packages could declare
their own "LTS" versions (if needed) and drop support for older
versions more freely in future development.
On Wednesday, March 11, 2015 at 8:13:11 PM UTC-4, Tim Graham wrote:
With the release of 1.8 coming up, it's time to think about 1.9!
I've suggested some dates below. The schedule is similar to the
intervals we used for 1.8 with the final release date planned for
about 6 months after 1.8 final (barring unforeseen delays, 1.8
will be released about 7 months after 1.7). Please voice any
thoughts or concerns. With this schedule it seems that any GSoC
work would likely be included in 2.0. If you have any big features
planned, please add them here:
https://code.djangoproject.com/wiki/Version1.9Roadmap
<https://code.djangoproject.com/wiki/Version1.9Roadmap>
July 20 - Alpha (feature freeze)
August 21 - Beta (only release blockers fixed after this)
September 18 - RC (string freeze for translations)
October 2 - Final
--
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/0df00068-112f-4e98-9201-78d6ba9ef97c%40googlegroups.com
<https://groups.google.com/d/msgid/django-developers/0df00068-112f-4e98-9201-78d6ba9ef97c%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/551FDF14.2080908%40gmx.net.
For more options, visit https://groups.google.com/d/optout.
