* Freeze mature MicroProfile APIs ready
to move to Jakarta.
* Move these APIs properly to Jakarta
* At the runtime level, resolve
org.eclipse.microprofile.* to jakarta.*.
* Make future changes under Jakarta.
This sounds very good. It enforces the notion of MicroProfile being an incubator for Jakarta EE. In MicroProfile more experimentation and brash ideas are allowed. Eventually when something is ready and stable enough it can be moved to Jakarta EE.
And indeed, as I proposed earlier as well, vendors can choose to support both versions in various ways, such as, indeed, resolving org.eclipse.microprofile.* to jakarta.*