Hi,
I think we don't need to issue the CCR for the release still in development.
However, for the final release, I feel like we need to issue the CCR to release GlassFish as "Jakarta EE compatible implementation" even with a minor updates.
On the other hand, It will take about two weeks for the CCR to be approved. so it may not be appropriate to issue it every patch release.
I'll check the CCR description again and if there are no clear rules, I will ask the jakartaee-platform.
Kind regards,
Hiroki
From: glassfish-dev <glassfish-dev-bounces@xxxxxxxxxxx>
On Behalf Of Scott Marlow
Sent: Friday, February 25, 2022 1:59 AM
To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>; arjan tijms <arjan.tijms@xxxxxxxxx>
Subject: Re: [glassfish-dev] About CCR for maintenance release
On 2/24/22 7:59 AM, arjan tijms wrote:
Hi,
As we're on a monthly cadence, should we add a job to issue the CCR as part of the release process?
Perhaps we should discuss if there should be CCR for all releases (alpha, beta, CR, final perhaps) on one of the Jakarta Platform or SPEC mailing lists.
Each CCR has to be reviewed, I am concerned with there being too many CCRs to review if implementations have to submit new CCRs even though they haven't changed to new EE SPEC API versions.
In the mean time would it be enough for the CI job to just post the TCK results on
https://glassfish.org/certifications/jakarta-platform as part of self validation?
Scott
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev