[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-spec.committee] GlassFish certification request; spec approval order
|
Right, any spec needing the full platform TCK really can’t be validated fully until wave 7 when that compatibility request for the platform TCKs are ready.
What if we create a placeholder certification request so that Managed Beans, EJB, etc. can have something to use to pre-stage in the interim.
> On Aug 12, 2019, at 4:02 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
>
> A quick update...
>
> Eclipse GlassFish 5.1 is passing the latest CTS, of course.
>
> But we're still sorting out the TCKs that are required but
> not included in the CTS - CDI, DI, and BV. We need to verify
> that we're using the latest (proposed) final versions of those
> TCKs and update the TCK results summary accordingly before we
> can submit the GlassFish certification request. Hopefully that
> will happen in the next day or so.
>
> The GlassFish certification results are for the full platform and
> web profile, and those specs can't be approved until all included
> specs are approved.
>
> Can we really approve (e.g.) the Managed Beans spec, which depends
> on the full platform TCK, *before* we approve the full platform?
> It seems like all of these specs that don't have their own standalone
> TCK and thus depend on the platform TCK need to be approved at the
> same time as the platform, and thus ought to be in wave 7. Right?
>
> We can review them in an earlier wave and make sure they're otherwise
> ready to go, but we can't start the ballot until the platform is ready.
> _______________________________________________
> jakarta.ee-spec.committee mailing list
> jakarta.ee-spec.committee@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
