Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [microprofile-wg] [DISCUSS] MicroProfile 7.0 Ballot verbiage straw poll
I have to disagree and the points of disagreement are in the document comments.

I don’t think there is any particular need to release MicroProfile concurrently with a Jakarta EE Core Profile release. The reality is that adoption takes a while in the ecosystem. It’s perfectly fine if a corresponding MicroProfile release happens a few months later. Similarly, runtimes can certify against either Jakarta EE Core and MicroProfile congruent with their product priorities.

Personally, I think Open Liberty is a great example to aspire to. They certified fairly promptly against Jakarta EE 10 Core and then equally promptly against MicroProfile 6, with MicroProfile 6 relatively promptly adopting the Jakarta EE 10 Core Profile.

From: microprofile-wg <microprofile-wg-bounces@xxxxxxxxxxx> on behalf of David Blevins <dblevins@xxxxxxxxxxxxx>
Sent: Friday, May 19, 2023 2:51 PM
To: Microprofile WG discussions <microprofile-wg@xxxxxxxxxxx>
Subject: [microprofile-wg] [DISCUSS] MicroProfile 7.0 Ballot verbiage straw poll
 
On May 19, 2023, at 11:05 AM, Reza Rahman <reza_rahman@xxxxxxxxx> wrote:

3 (Microsoft). Additional comments added in the document itself. This is essentially status quo today and implementations like Open Liberty do it well.

Just to clarify, we haven’t yet had any success with a Core Profile implementation being able to claim MicroProfile certification on the day of the Core Profile release.

Number 3 would still involve significant change the status quo to fix what hasn’t been working.  The change would be we can no longer follow our own release schedule.

Back to the top