Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [microprofile-wg] [microprofile] Re: MicroProfile 5.0 Compatible Certificate Request - Open Liberty 22.0.0.1

We will need to formalise this process after some initial discussion. We can discuss in today's call and then take it from there.
Thanks
Emily

On Fri, Jan 21, 2022 at 1:37 AM Roberto Cortez via microprofile-wg <microprofile-wg@xxxxxxxxxxx> wrote:
In the meantime, I suggest we use the Jakarta EE TCK process to create a CCR and have lazy consensus voting on it. Then the CCR is accepted after 14 days (with no -1).

I believe we discussed this before and the decision was that we needed to officially have the process in place. I’m not sure that saying here that we will use the Jakarta one count as official. We may need to have a vote on it first.

Cheers,
Roberto

On 20 Jan 2022, at 03:11, Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx> wrote:


Hi Emily,

The Steering Committee explicitly said that they were not going to create a compatibility program or logo. The proposal you reference in the issue is out of bounds because it violates both the letter and spirit of the resolution that was adopted by the Steering Committee.

Thanks ... Paul




On Wed, Jan 19, 2022 at 3:22 PM Emily Jiang via microprofile-wg <microprofile-wg@xxxxxxxxxxx> wrote:
Thank you Paul for the info! Maybe the wording I used was wrong. I referred to this issue. Can you confirm whether this issue is legally allowed?
Thanks
Emily



On Wed, Jan 19, 2022 at 7:15 PM Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Emily, 

To your statement of “we should create our own community-owned compatibility logo”, that is inconsistent with what the working group decided last November. There is no “community owned” logo; the working group has decided there is no MicroProfile compatible logo.

Please follow the link below to see the Steering Committee's resolution and the guidance provided by me to the working group after the Steering Committee passed the resolution to not have a compatibility program and logo.


Thanks ... Paul


On Wed, Jan 19, 2022 at 6:59 AM 'Emily Jiang' via MicroProfile <microprofile@xxxxxxxxxxxxxxxx> wrote:
Hi Roberto,

We definitely need to revisit the TCK certification process since MicroProfile has decided not to use the EF trademark programme and no EF approved compatible logos. We should create our own community-owned compatibility logo this year. I logged an issue to create a compatible page and create a community-owned logo.

Since we don't have the required process, we have to redefine the process ourselves. 

David, would you like to update the PR to reflect the current status? If there is no update this week, I can volunteer to take over to directly make some updates. We can then discuss this in next week's technical calls. 
In the meantime, I suggest we use the Jakarta EE TCK process to create a CCR and have lazy consensus voting on it. Then the CCR is accepted after 14 days (with no -1).

Thoughts?

Thanks
Emily

On Wed, Jan 19, 2022 at 12:50 PM Roberto Cortez <radcortez@xxxxxxxxx> wrote:
Hi Emily,

Congratulations on the OL release. Well done :)

Regarding the CCR, I believe we had a blocker with https://github.com/microprofile/microprofile-wg/pull/96, which was required to be in place before any CCR being accepted. I’ve sent an email about it a few days ago, but no response, since we have a few CCR’s for 4.x which are still open.

Are we ok to accept the CRRs with the TCK process?

Thanks!

Cheers,
Roberto

On 18 Jan 2022, at 21:52, Emily Jiang via microprofile-wg <microprofile-wg@xxxxxxxxxxx> wrote:

I am pleased to say Open Liberty 22.0.0.1 released today fully supports MicroProfile 5.0. A compatible implementation request was filed here for both Java 11 and Java 17. Please review and comment on the git issue if applicable. If there are no objections within 14 days, the issue will be accepted.

Thanks
Emily


_______________________________________________
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/microprofile-wg



--
Thanks
Emily


--
You received this message because you are subscribed to the Google Groups "MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile+unsubscribe@xxxxxxxxxxxxxxxx.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/CAECq3A_YzB4Ycx6vcMOcF2fec%3DG%2BCyY3aeV3WuhiB3n38b9rwg%40mail.gmail.com.
_______________________________________________
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/microprofile-wg


--
Thanks
Emily

_______________________________________________
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/microprofile-wg
_______________________________________________
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/microprofile-wg

_______________________________________________
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/microprofile-wg


--
Thanks
Emily


Back to the top