Re: How do I request a new feature in 1.11.x?

Those "features" were related to changes in Django 1.11 that caused problems that older versions of Django didn't have.

On Wednesday, October 11, 2017 at 11:12:33 AM UTC-4, Chris Beck wrote:

that's what I expected but 1.11.1 and 1.11.2 each added a minor feature

On 11 October 2017 at 10:03, Tim Graham <timog...@gmail.com> wrote:

No, Django 1.11.x won't receive new features. The supported versions policy is the same for that release series as for other releases.

https://docs.djangoproject.com/en/dev/internals/release-process/#supported-versions

On Wednesday, October 11, 2017 at 12:01:06 AM UTC-4, Chris Beck wrote:

Thanks James,

I wasn't expecting action from my email, just advice on how to prompt for it - which you provided!

Cheers,

Chris

On 10 October 2017 at 23:57, James Schneider <jrschn...@gmail.com> wrote:

On Oct 10, 2017 8:50 PM, "Chris Beck" <cb...@railkey.net> wrote:

So there is a new feature being worked on in the master branch:

https://code.djangoproject.com/ticket/28668 (adding ON CONFLICT DO NOTHING support to bulk_create)

How might I add a request that that feature be included in a future 1.11 release if possible? Since 1.11 is the last Python2 release and will be around for a few more years are new features being contemplated?

Cheers,

Chris

This is the end-users list, and most of the devs that would make such a decision aren't watching. You may have better luck with a solid answer on the Django dev list.

Personally, I would follow up directly within the ticket. The activity a ticket has is an informal indication of community interest and may garner more attention from the devs.

I believe that releases are feature locked, but given the deprecation of 2.7 support being a major blocker for upgrade to some environments, there may be a cause for an exception to backport features.

I'm not a dev, though, just a guy who occasionally writes code. My opinions mean nothing and I'm fine with that. ;-)

-James

--
You received this message because you are subscribed to a topic in the Google Groups "Django users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-users/XiH6z9xxu5Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2Be%2BciWUExY99q%3DndG%3DVkM61x0VYrWBp5NXWBNGCgfnOzV0y%3DQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Christopher Beck

cb...@railkey.net

+1.514.431.7759

--
You received this message because you are subscribed to a topic in the Google Groups "Django users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-users/XiH6z9xxu5Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/edffec9c-0880-482a-a2fe-48efefc307ac%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Christopher Beck

cb...@railkey.net

+1.514.431.7759

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/78fd5969-d4e6-4d3c-ac01-1fbd0781d560%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.