+1 payara (After discussion within the team, we decided to vote positive for proposal 1)
Ballot text:
"Resolved, the MicroProfile Steering Committee approves the MicroProfile 7.0 proposal 1 to support a minimum Jakarta EE Version"
This is the vote thread. Feedback/discussion, if needed, should be given in a separate thread with the subject of [DISCUSSION][Proposal 1][MP 7.0].
A Steering Committee Representatives vote is requested. Please respond with +1 (positive), 0 (abstain), or -1 (reject). Any feedback that you can provide to support your vote will be appreciated.
This ballot runs for seven days, so it ends on June 12th, 2023. The ballot requires a Simple-majority positive vote of the Steering Committee members. There is no veto. Community input and Community votes are welcomed. However, only the votes delivered
by Steering Committee Representatives will be counted.
----------
Proposal
1: MicroProfile releases support a minimum Jakarta EE versions
-
The minimum Jakarta EE version would be specified in the
MicroProfile umbrella specification like it currently is in the component specifications.
-
The Jakarta EE Core Profile API jar will be marked provided
in the pom.xml as they are for the component specifications.
-
MP Implementations must pass the Jakarta EE TCK for the version
and profile they implement.
-
It is expected that MP implementations and community will
actively be participating in new EE releases, passing both TCKs and surfacing compatibility issues eagerly.
-
If there are backwards compatibility issues that would prevent
an implementation from passing the respective TCKs, those kinds of issues would need to be addressed through the specification process (i.e. a major, minor or service release).
-
MP Certification Requests (CCRs) must specify the exact
Jakarta EE version and profile was implemented and passed in their certification results.
Q&A