This is really a service release, with no impact on the user or implementors (both implementations has already tested against this)
As you know, due to the Eclipse process, we could not do a service release, so, as agreed we bumped the version to a 1.1 even if there is no new functionality, no breaking changes etc.
I think we (MicroProfile) need to be careful that our process is not busy killing any progress and inovation. We have already lost a lot of momentum in most specs due to the "waiting for the workgroup" and now the process is making it difficult to get going again.
I want to point everyone to the agile manifesto, specifically people over process.
I have worked in enough businesses where too rigid process enforment killed any inovation and progress and I think we need to be careful in how we proceed.
I understand that process is needed, but this is an exceptional case where we need a small fix, and the current effort is just not worth it, and anyone that cared to take part in this workgroup (and the same argument for the OpenAPI workgroup) would know that.
So, back to what is needed to get this out. Are you saying that I need to add a part in the actual spec document, that states that we previously had an error in our TCK that is now fixed ? And that we forgot to make a annotation available on a parameter, and that is now fixed ? That seems unnecessary.
Let me know.