Re: [jaxrs-dev] JAX-RS Kick-Off: Commiters, Start Your Engines!

[Kevin Sutter <kwsutter@xxxxxxxxx>]

Markus,

I think I mis-read your original post...  I thought you were committing more changes to master, which I was trying to discourage at this point.  After reading your reply to my note and re-reading the original post, it looks like you were just pointing out the initial contribution was committed.  And, you were trying to set up some ground rules for future contributions.

To that end, we just published some ground rules from a PMC perspective:  https://www.eclipse.org/ee4j/news/?date=2018-02-16

Until we get complete Java EE 8 compliance with the EE4J project, we have to introduce some of these rules and guidelines.  The PMC is a small team, so we will are asking for all of the EE4J projects to help introduce and promote these guidelines.  Basically, we need Master to stay pristine except for bug fixes to allow the Java EE 8 TCK and CTS to execute successfully.  Additional branches (sandboxes) are up to a project's direction.

We are working diligently with Oracle to get the TCK's contributed.  Those components with individual standalone TCKs will be easiest ones to contribute.  The rest of the CTS buckets and associated harnessing will take a bit more time. But, everyone is pushing very hard to get all of CTS and TCKs in Eclipse as efficiently as possible.

Adding people to mailing lists without their consent isn't always a favorable act...  Please do whatever you can to encourage people to subscribe to the list.  Maybe send out a plea to the old jax-rs mailing lists?  Maybe Tweet, if you are active on Twitter.  We'll need to encourage everyone to get involved.

Thanks again for participating!

Kevin

On Fri, Feb 16, 2018 at 7:26 AM, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

Kevin

 

thank you for sharing your thoughts.

 

Actually I know all that and can assure you that my commits will be supportive for Java EE 8 compatibility, not conflicting it. As a former Jersey committer and JCP JAX-RS Expert Group member, and as an individual Eclipse Foundation Member, be assured that I know very well what I do and what the impact is.

 

Regarding CTS, it would be great if the PMC could ask Oracle to provide the JAX-RS TCK as soon as Jersey is passing it (so we know the TCK is error-free in itself).

 

Also it would be great if the PMC could add all JAX-RS committers to the jaxrs-dev mailing list. Apparently neither the EMO nor the project lead did that, and as you say, one cannot add himself.

 

-Markus

 

 

From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@eclipse.org] On Behalf Of Kevin Sutter
Sent: Donnerstag, 15. Februar 2018 17:34
To: jaxrs-dev@xxxxxxxxxxx
Cc: dmitry.kornilov@xxxxxxxxxx
Subject: Re: [jaxrs-dev] JAX-RS Kick-Off: Commiters, Start Your Engines!

 

Hi Markus,

Since I just joined this email list, I don't have the original message to reply to, so here's a link for other readers...
https://dev.eclipse.org/mhonarc/lists/jaxrs-dev/msg00001.html

Also, this email distribution list is still pretty light...  People have to be added explicitly...  When I signed up this morning, there were only 3 people on the list.  That is probably you, me, and Dmitry...  Not a large contingent yet.  So, we can't count a lack of responses as non-caring.

 

Have to love your enthusiasm though!  But, we probably have to cut back on the throttle a bit...  The number one priority of the EE4J project is to ensure we're compatible with Java EE 8.  The code that Oracle is contributing to Eclipse needs to pass all of the Java EE 8 compatibility tests, known as the CTS.  This test suite is comprised of somewhere around 45,000 tests.

So, we need to be careful on what type of changes are being put into the github repository at this point.  The move to Eclipse is still new to a few people and we need to wait for a bit more participation before we make too many changes.  If there are developers from the old Expert Group that need to subscribe and participate, please encourage them.  Eclipse is a very open and welcoming community.  It should be very easy for any developer to sign up without issue.

I don't have enough background on jax-rs to know whether your commits will affect java ee 8 compliance.  I'll let others decide.  But, just be aware that we may need to move your changes to another branch, or we may need to cut a separate branch, in order to make progress with Java EE 8.  Somebody will definitely reach out to you before that happens though...

Thanks for your assistance and understanding, Markus!

-- Kevin Sutter

Member of EE4J PMC

 

_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jaxrs-dev