discussion of stability for internal APIs

[trevnorris]

Filing for discussion in the next TSC meeting.

Ref: #2026 (and its linked threads)

Main point of discussion is: Do internal, but publicly exposed, APIs need to remain API stable across minor releases. As interpreted from the API Stability Policy here: https://github.com/nodejs/dev-policy#stability-policy

The hopeful outcome is to come to consensus on how to interpret that section, and file any changes the policy as necessary.

This issue is only a placeholder, and discussion on this topic has happened ad nauseam elsewhere. I do not intend further discussion to happen on this thread.

[Fishrock123]

@nodejs/tsc It would be helpful if ya'll could give it a bit of a read-through beforehand.

[Fishrock123]

I think I found the key bits in there:

(b) it is clear that the Implicit API being modified was originally intended for internal use as part of the underlying implementation (as opposed to being targeted at developers); or

&

That said, changes to any of the APIs should not be made lightly as there is currently no reliable means of determining in advance the impact any change may have on existing applications and modules. Collaborators must use their best judgement to determine whether any given change is "technically backwards incompatible but in practice should not be", then approach landing the change accordingly.

[cjihrig]

@trevnorris these might also be relevant:

nodejs/dev-policy#37
nodejs/dev-policy#50

[trevnorris]

@cjihrig Thanks for the additional information.

Discussion was had and recorded in meeting notes.

[trevnorris]

Link to meeting issue: #58