Closed abique closed 2 years ago
OK, I've reverted the latest change as I wasn't sure about it. Let's go :-)
My only question which I mentioned on discord: Do we want to put the menu extension in here in draft so we can try and implement it in bitwig/surge?
My only question which I mentioned on discord: Do we want to put the menu extension in here in draft so we can try and implement it in bitwig/surge?
Is it ready? I remember that it still had open spec questions and there is no PR yet for it. I think we can move on with 1.1.0 and as soon as the menu one is ready we make 1.2.0, unless the menu ext can be ready in the next few days?
My only question which I mentioned on discord: Do we want to put the menu extension in here in draft so we can try and implement it in bitwig/surge?
Is it ready? I remember that it still had open spec questions and there is no PR yet for it. I think we can move on with 1.1.0 and as soon as the menu one is ready we make 1.2.0, unless the menu ext can be ready in the next few days?
I would recommend to wait and leave specs in draft/ until at least two implementations exist.
Fast iterations are great in the pre-1.0 aera or in draft state but not once things are official API/ABI and should not be deprecated/replaced for a couple years.
It is really easy for an implementation to support an additional "clap.foo.draft/99" interface string next to "clap.foo", but really hard to fix up an interface that lacks a tiny slot for an additional integer as state_context_t has just demonstrated.
Sorry, I convert back to draft, because I want a bit more time regarding voice-info.