On 12/07/2014 04:37 PM, Russell Keith-Magee wrote: > For my money, the role of this policy change isn't to introduce > instability into Django's process. The role is to give us permission to > introduce features which we might not otherwise land (or might delay in > landing) due to fears over whether the public-facing API is suitable for > use.
That sounds good in theory -- but are there any examples, ever in Django's history, of a feature we otherwise wanted, but chose not to land because we weren't sure enough that the API was right? "Delay landing" is a different story. If we're unsure enough of an API to delay landing the code, then I think "delay landing until we're more confident" is a much better choice than "land it anyway but with a provisional tag." Carl -- 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 [email protected]. To post to this group, send email to [email protected]. 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/5484F4BE.8070708%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
