<@U02TSJJT9DJ>: it took way too long, but i finall...
# developmentw
witty-crayon-22786
01/20/2023, 7:14 PM@wide-midnight-78598: it took way too long, but i finally got around to refreshing the Plugin API Stability project, including doing a bit of triage to prioritize things.
👀 1
witty-crayon-22786
01/20/2023, 7:15 PMthere were definitely some items mentioned in your presentation that don’t have corresponding issues: i’ll add notes for them now.
🎉 1
witty-crayon-22786
01/20/2023, 7:22 PM…but please add any that i missed!
👍 1
c
curved-television-6568
01/20/2023, 7:42 PMwill the Plugin API be potentially considered stable when all issues in this project are closed?
w
witty-crayon-22786
01/20/2023, 9:08 PMmm, as discussed in the last meeting, it’s possible that stabilization is more incremental than that: that we come up with an annotation or convention to mark things stable, and then are able to start stabilizing some APIs sooner
witty-crayon-22786
01/20/2023, 9:09 PMand debate whether to stabilize individual APIs based on the list of open issues
witty-crayon-22786
01/20/2023, 9:10 PMi’ll add a draft item for that.
c
curved-television-6568
01/20/2023, 9:16 PMright. yea that make a lot of sense. no need to treat the whole plugin API as a single entity.
w
wide-midnight-78598
01/21/2023, 1:35 AM🤷 It can be hard as a plugin consumer if pieces of the API are considered stable, while pieces are experimental - as it practically means your usage is experimental.
But, at the same time, I'd take any stability marker over no stability marker - so any forward progress is a win in my eyes 🙂
c
curved-television-6568
01/21/2023, 2:08 AMwe should be able to present the current stability grade per API type (even if grouped in larger sets or not) in an accessible way through documentation, like in the Explorer as one source for this (upcoming…):