On Thu, Jun 30, 2011 at 7:33 PM, Anand Kumria <[email protected]> wrote: > Hi, > > In ticket #16255 <https://code.djangoproject.com/ticket/16255>, > changeset https://code.djangoproject.com/changeset/16423 raises the > minimum supported PostgreSQL version to 8.2 > > However the PostgreSQL support policy, <http://wiki.postgresql.org/ > wiki/PostgreSQL_Release_Support_Policy>, indicates that 8.2 will be > end-of-life at the end of the 2011 > > I think it would be better to raise the documented minimum version to > 8.3 (EOL is in 2013). Actually modifying Django to take advantage of > features available in 8.3 (or later) could be done at another time > though. > > Should I re-open the ticket to indicate this, send in a patch for this > doc. change, or is this email enough?
Hi Anand, I'll fully acknowledge that PostgreSQL 8.3 is better than 8.2, but I'm not aware of any feature in Django that hinges on support of 8.3, or any plans to introduce such a feature. On top of that, 8.2 isn't deprecated *yet*, and I would like to think that we could get Django 1.4 out the door before the end of 2011, so we'd be deprecating a version of PostgreSQL slightly before it is EOL'd, without any pressing technical need. "Because we can" isn't a good enough reason to deprecate something in my opinion, because in a community as large as Django's, every deprecation affects somebody. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
