Sure. I is not my intention to contravene Mike or any direction
from Eclipse. Ultimately, it's their call. Certainly it will be
good to have clear directions.
Ed,
Unfortunately, this was not
clear...
I really thought that Mike was putting the brakes on doing any
type
of release of Jakarta EE components until the agreements are
finalized.
I fully understand your approach outlined below that if no
changes
were done to the APIs, then we *should* be okay. I didn't think
Mike
wanted to take that chance... That's what I heard on these
calls.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Java EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From:
Ed Bratt
<ed.bratt@xxxxxxxxxx>
To:
EE4J PMC Discussions
<ee4j-pmc@xxxxxxxxxxx>, David Blevins
<dblevins@xxxxxxxxxxxxx>
Date:
08/16/2018 04:54 PM
Subject:
Re: [ee4j-pmc]
JAX-RS API Release
Sent by:
ee4j-pmc-bounces@xxxxxxxxxxx
David (and PMC):
(Jumping in because Dmitry is on holiday.)
I believe that these are the "equivalence"
releases
for Eclipse GlassFish 5.1. The goal with this first set of
Eclipse Jakarta
EE components is that they have exactly the same API
compatibility as those
used in GlassFish 5.0 (i.e. both are Java EE 8 compatible).
Since they will be tested and certified for
compatibility,
I believe that this is fully in compliance with the terms of
the TCK agreements
that are to be signed. Further, I think this is within the
scope of agreements
already in place since no specified APIs are changed.
I have asked Oracle developers to perform TCK
verification
for any components ready for Eclipse Release Review before the
TCK agreement
with Eclipse Foundation is signed. The TCK agreement must be
finished before
we can finalize Eclipse GlassFish 5.1 and use any Java EE
branding. We
are working to complete that discussion.
Once the agreement is in place, we can do this
compatibility
testing on Eclipse resources.
I thought that we'd discussed this at Steering
Committee,
but perhaps not clearly enough. I'd be happy to answer
additional questions,
here in e-mail, or at the meeting.
Cheers,
-- Ed Bratt
On 8/16/2018 2:32 PM, David Blevins wrote:
It's a tough one. My understanding of where
we're
at is that releasing code under the javax namespace will break
the temporary
contracts in place that explicitly forbid it. Our chances of
getting
the contracts we want will likely not increase if we break the
ones already
made. If Dmitry is asking for a release, then I'm out of the
loop.
It's a good thread and I'm also interested in how
this
goes.
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852
On Aug 16, 2018, at 1:55 PM, Markus KARG <markus@xxxxxxxxxxxxxxx>
wrote:
Hello PMC,
the JAX-RS API team is currently
preparing
release 2.1.1 (i. e. EE4J_8). We do not have received neither
TCK nor spec.
We do not have an ageement with Oracle. We just have the API
itself (Java
source code). Dmitry filed an issue requesting an initial
release. So does
the PMC want us to…
…release immediately even without
TCK
and spec?
…wait until all of that is here
and release
then?
…something else…?
Thanks
-Markus
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
