My notes from the meeting say "experimental API language", so I may have taken an adjective too literally when I made this.
Nevertheless, the key thing _I_ want to see is for us to commit to putting release notes out for some of Django's APIs that aren't necessarily considered stable. The 1.7 database API stuff was the main catalyst for this; those are changes and APIs we should have documented, and fall somewhere above "internal" (as we expect people to build third-party database backends), but not tie ourselves into a 3-release deprecation cycle for. How about we change the label from "Experimental" to something like "Unstable", but keep the same provisions - documentation called out as "unstable feature", separate section in the release notes, etc. That establishes a clear level between "internal and we don't care about it" and "stable and publicly documented". The alternative is to change the DEP to just say we're going to start putting release notes up for certain internal APIs, and then somehow list the ones we will somewhere (probably on the API stability page). Andrew On Sat, Dec 6, 2014 at 1:02 PM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > On 6 déc. 2014, at 10:05, Carl Meyer <c...@oddbird.net> wrote: > > > As the DEP notes, our backwards-compatibility policy already includes a > > longstanding carve-out for anything documented within the "internals" > > section of the docs. We haven't made much use of this for documenting > > actual internal APIs (most of that section of the docs is about > > contribution process), but we could. > > Like Carl, I believe “internal” is an established concept that fits our > needs > better than “experimental”. > > To me “experimental” sounds much like an ill-defined gray zone between > private and public. > > -- > Aymeric. > > > > > -- > 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/A3D3D45A-19CE-44D4-82DA-84AA45EDA586%40polytechnique.org > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAFwN1uqV%2BYbu%3DQgCy3W5AC3aFDX_0W4YzUQLT22RH3h01KLLvg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
