Correct, Lukas. But,
as long as these components have staged their final versions of the APIs,
then Steve should still be good. If an issue is raised with one of
these staged APIs, then we will have to adjust. But, we should feel
comfortable with using the staged APIs at this point. --------------------------------------------------- Kevin Sutter STSM, MicroProfile and Jakarta EE architect @ IBM e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620 (office) LinkedIn: https://www.linkedin.com/in/kevinwsutter
On 11/1/20 6:26 PM, Steve Millidge
(Payara) wrote: > I have cut an RC2 of GlassFish today. This has the final version of
all > the Jakarta APIs. IMHO this should be the version we should focus
on as > the Compatible Implementation of Jakarta EE to get the platform > specification to ballot and Jakarta EE released.
agree. Only note that release reviews for some specs/APIs should conclude on Wed Nov 4, so they cannot be pushed to central before that
What is the deadline for these CIs to be in central? Given that release
review can conclude on 1st and 3rd Wed of the month and should be running for a week, I'm not sure a date before Nov 18 is reachable, unless release reviews for all of remaining CIs are set to conclude this
Wed, Nov 4.
> The reason I think these can follow is that all the Eclipse components
> are going to have to have a release review and appear in maven central
> before they can be incorporated into GlassFish Final and the timelines
> of that are out of control of the GlassFish project. > > On a related point I want to cut final versions of GlassFish dependent
> components that are in the control of the GlassFish project and put
them > out for release review e.g. HK2, Shoal, HA-API, JSF-templating and
> Woodstock. Does anybody object to releasing those as is?