Re: [ee4j-pmc] JAX-RS API Release

[David Blevins <dblevins@xxxxxxxxxxxxx>]

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