Kevin Sutter wrote on 6/5/19 6:18 AM:
Bill,
> It's
not our plan to hold up this release until other compatible
implementations
are available. If you think we need to do that, you should
bring
that up at the Steering Committee, although that would clearly
blow our
schedule.
I've tried to
be very clear that having additional Compatible Implementions is
a requirement
for Jakarta EE 8.
I'm afraid you've failed. :-) Seriously, yesterday was the first
time any of us at Oracle had heard that this was even being
considered. Last we knew none of the other implementations expected
to be compatible until months after release.
And, I don't
think this blows the schedule. I
know that Eclipse Glassfish, Wildfly, and OpenLiberty are all
active with
running the Jakarta EE TCK with varying results. We should
probably
identify a milestone date on the schedule for CIs to be 100% TCK
passing
in order to be included with the announce. Since this activity
is
independent of the release and being driven by the respective
open-source
development communities and vendors, it should not affect the
schedule.
As I said before, if other implementations can be compatible on the
proposed schedule, that's great! And I agree we should decide on
what date they need to prove compatibility to be included in the
announcement.
Also, both you
and Mike D have indicated a final release should be required...
But,
I don't know how we keep to the schedule if we have to produce a
new release
of Glassfish (for example) that uses the updated APIs and then
do the final
testing -- all of this before we submit for the Release Review.
This
just doesn't work. I think we need to re-address what is really
required
for a Compatible Implementation prior to the Release Review.
Sigh. I guess my message wasn't clear at all. We're not producing
a new release of GlassFish. We already have a final release of
Eclipse GlassFish 5.1. That's what we'll use with this approval
process.
If we were to produce a final release of GlassFish for this
Jakarta EE 8 release, we would have all the work done and staged at
the time we submitted it for the release review. Once the release
was approved we would just "push the button" and release the staged
artifacts. I don't see why this is complicated. The reason we're
not doing that now is to save time in the schedule.
|
