| Re: [glassfish-dev] About CCR for maintenance release |
Hi,
Good question. I've made sure that each and every release passes the EFTL certification and certification-web. See the jobs here: https://ci.eclipse.org/jakartaee-tck/view/EFTL-CERTIFICATION-JOBS/
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
Kind regards,Arjan Tijms
Hi,
I have a little concern about maintenance release.
Since we issued the GlassFish 6.1 CCR last year[*1], we have published several maintenance releases[*2], do these not need the CCR?
[*1] https://github.com/eclipse-ee4j/jakartaee-platform/issues?q=is%3Aissue+GlassFish+is%3Aclosed+label%3Acertification
[*2] https://glassfish.org/
Kind regards,
Hiroki
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev
_______________________________________________ glassfish-dev mailing list glassfish-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev