Re: 1.9 release planning

2015-04-04 Thread Thomas Tanner
I think rare LTS releases and frequent (6month) incremental upgrades are a good compromise. Third-party packages should support LTS releases and at least the latest Django version. They may drop support for earlier non-LTS releases. Either you stick with the LTS release or you go with the cutting

Ordering of fields in subclasses of a form

2014-12-06 Thread Thomas Tanner
Hi, I've submitted a pull request https://github.com/django/django/pull/3652 for the often requested feature "Easy way to customize ordering of fields on forms that use inheritance". I'd appreciate some feedback https://code.djangoproject.com/ticket/5986#comment:32 cheers, -- You received this

Re: condition decorator: if-unmodified-since support and updated etags

2014-04-16 Thread Thomas Tanner
thank you. It's submitted https://github.com/django/django/pull/2573 On 16.04.14 18:24, Tim Graham wrote: > The mailing list is typically only required for "major" features. I'm > not entirely sure the extent of what you are proposing, but I don't > think it'll need a mailing list discussion -- a

Re: condition decorator: if-unmodified-since support and updated etags

2014-04-16 Thread Thomas Tanner
Hi Tim, I'm a bit confused by: On 16.04.14 16:51, Tim Graham wrote: > https://docs.djangoproject.com/en/dev/internals/contributing/ Requesting features: First request the feature on the django-developers list, not in the ticket tracker. It’ll get read more closely if it’s on the mailing list.

condition decorator: if-unmodified-since support and updated etags

2014-04-16 Thread Thomas Tanner
Hello, I have implemented support for the If-Unmodified-Since header http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.28 in the condition decorator and added an parameter to support updating of the etags for write operations