Make scap plugins more useful and usable outside the core scap team by defining (mainly documenting) which scap APIs can be considered stable and safe to rely on from plugin code.
The main thing I had in mind here was to clearly differentiate the stable parts from the internal APIs which should be considered use-at-your-own-risk or possibly even private.
I think it meant more docs and a set of APIs which are 'blessed' as stable and usable.
The main thing I had in mind here was to clearly differentiate the stable parts from the internal APIs which should be considered use-at-your-own-risk or possibly even private.
After all those years:
So I don't think there is any need to define a stable API. It is defacto stable.