Re: 1.9 release planning
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 edge with all dependencies. Advantages of release early, release often are that new features have more time to mature before a LTS release, you don't have to risk using the unstable HEAD for new features, and more feedback from users. On 04.04.15 14:30, Tim Graham wrote: > 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. > > 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. -- 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/552017D7.6020907%40gmx.net. For more options, visit https://groups.google.com/d/optout.
Ordering of fields in subclasses of a form
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 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/54832845.9010001%40gmx.net. For more options, visit https://groups.google.com/d/optout.
Re: condition decorator: if-unmodified-since support and updated etags
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 Trac ticket is sufficient. > -- You received this message because you are subscribed to the Google Groups "Django developers" 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/534EB557.3020101%40gmx.net. For more options, visit https://groups.google.com/d/optout.
Re: condition decorator: if-unmodified-since support and updated etags
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. This is even more important for large-scale feature requests. We like to discuss any big changes to Django’s core on the mailing list before actually working on them. If core developers agree on the feature, then it’s appropriate to create a ticket. Include a link the discussion on django-developers in the ticket description. As with most open-source projects, code talks. If you are willing to write the code for the feature yourself or, even better, if you’ve already written it, it’s much more likely to be accepted. Just fork Django on GitHub, create a feature branch, and show us your work! while in django/CONTRIBUTING.rst: **Warning: non-trivial pull requests (anything more than fixing a typo) without Trac tickets will be closed!** `Please file a ticket`__ to suggest changes Does this mean the steps are 1. ask on this mailing list whether my feature request is OK 2. create a ticket with the link to discussion 3. create a pull request referencing the ticket Or can I skip step 1, and even step 2? thanks -- You received this message because you are subscribed to the Google Groups "Django developers" 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/534EAA83.30609%40gmx.net. For more options, visit https://groups.google.com/d/optout.
condition decorator: if-unmodified-since support and updated etags
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 http://tools.ietf.org/id/draft-reschke-http-etag-on-write-09.txt Where should I submit my patch? cheers, -- You received this message because you are subscribed to the Google Groups "Django developers" 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/534E8C29.500%40gmx.net. For more options, visit https://groups.google.com/d/optout.
