On Tue, Aug 7, 2012 at 8:40 AM, Mike Dewhirst <mi...@dewhirst.com.au> wrote: > Russell > > This might be slightly off-thread. Since 1.5 will be Python 3, would you > consider making 1.4 a long-term-support version?
Django 1.5 will be the first Django release to officially support Python 3, but it will still support Python 2. We're not going to go cold-turkey on Python 2 -- we'll be supporting Python 2 for a while yet. > I know a couple of large organisations who simply won't consider non-LTS > open source kit. The core team has talked about this sort of approach in the past -- usually in the context of moving to a faster release cycle (e.g., release every three months, but nominate a LTS release every 18 months or so). However, those discussions usually stall on the problem of actually doing a faster release, which historically, we haven't been good at doing. I'd be interested in hearing other opinions about this. Out there in the "real world" (™), how long does Long Term Support have to be in order to be practically useful? Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
