Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Plan B Deliverable for JakartaOne and OC1?

IMHO, we must have a new alternative "headline" prepared as I mentioned in our Steering Committee call today.   I think the reduced scope of the Web Profile as suggested by Kevin is probably our most viable, achievable option by September 10, with the Full Profile achievement announced at EclipseCon Europe 2019 in October.  I certainly hope we can reach consensus on this position.

Best regards,
Dan

Dan Bandera
(512) 286-5228
Program Director, Blockchain, Istio, Java technologies, Node.js
IBM Open Technologies, Austin, Texas
The OSGi Alliance ( osgi.org ) President and Board of Directors





From:        David Blevins <dblevins@xxxxxxxxxxxxx>
To:        Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:        2019-08-06 05:21 PM
Subject:        [EXTERNAL] Re: [jakarta.ee-spec.committee] Plan B Deliverable for JakartaOne and OC1?
Sent by:        jakarta.ee-spec.committee-bounces@xxxxxxxxxxx




> On Aug 6, 2019, at 2:32 PM, Kevin Sutter <sutter@xxxxxxxxxx> wrote:
>
> What about if we would limit our focus to just Jakarta EE 8 Web Profile?

That's an *extremely* compelling idea.

Given how intertwined the Full and WebProfile TCK is (the same), it may not pan out, but that doesn't mean we couldn't prioritize Web Profile specs first.  If we're clever, maybe there's something we can do about the TCK issue, such as simply name it "jakartaee-webprofile-tck" and declare it can only be used for web profile certification despite having more tests.

Also brainstorming out loud.  Certainly worth talking about at tomorrow's spec meeting.

-David



_______________________________________________
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





Back to the top