To be fair, at the JCP we allowed up to 30 days between spec
approval and final release of the RI. That was generally not needed
for simple standalone specs, but was needed for GlassFish. I would
be willing to consider something like that here. I'm just not in
support of an arbitrary time between approval and release.
Bill Shannon wrote on 6/7/19 9:58 AM:
Kevin Sutter wrote on 6/7/19 8:59 AM:
There needs
to be some open-source Compatible Implementation available
when the Spec is promoted to the Release Review. This may be
Glassfish, but it may also be OpenLiberty or Wildfly or TomEE.
It has to show and prove that the Spec is implementable and
that the TCK works as advertised. It does not have to be
Production quality and provide all of the associated bells and
whistles.
Don't confuse "final" and "production ready".
I'm not saying anything about the quality of the release, only
that it's something that the project/vendor producing it thinks is
"done" and ready for use. Bells and whistles can be added in a
follow on release, or in a separate product release.
Eclipse GlassFish 5.1 can be done, and Payara Server 5.1 may still
require a lot of work before it's ready for release.
_______________________________________________
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
|
