Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] VOTE: Specifications to Prune inJakarta EE 9
if that is the case, i recommend that the voting on Jakarta EE gets put into discussion b/c it won't lead to long term health. 


On Wed, Nov 20, 2019 at 1:01 PM Kevin Sutter <sutter@xxxxxxxxxx> wrote:
Werner,
All Platform Committers get a vote, regardless of organization or vendor affiliation.  This was discussed at our Platform Dev call earlier this week.  The minutes are here:
https://eclipse-ee4j.github.io/jakartaee-platform/minutes/2019-11-19.html

Thanks!

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta 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:        Werner Keil <werner.keil@xxxxxxx>
To:        jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date:        11/20/2019 14:49
Subject:        [EXTERNAL] Re: [jakartaee-platform-dev] VOTE: Specifications to Prune inJakarta EE 9
Sent by:        jakartaee-platform-dev-bounces@xxxxxxxxxxx


A good reminder about who has Voting privileges here?

And especially in Rudy’s case, as he works for Payara, do member companies like Payara, Tomitribe, IBM, Oracle etc. have one vote per Company (like it used to be in the JCP) or do committers regardless of their afiliation have one vote each?

 

Werner

 

Sent from Mailfor Windows 10

 

From: Rudy De Busscher
Sent: Monday, November 18, 2019 08:01
To: jakartaee-platform developer discussions
Subject: Re: [jakartaee-platform-dev] VOTE: Specifications to Prune inJakarta EE 9

 

+1 (not a platform committer)

 

Rudy

 

On Sun, 17 Nov 2019 at 22:42, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

+1

Steve Millidge (Payara) wrote on 11/17/19 8:56 AM:

See previous email for context.

 

All committers please vote on this proposal for specifications to be pruned from the Jakarta EE 9 platform specifications.

 

The following specifications will be *removed* from Jakarta EE 9 Full profile specification.

- Jakarta XML Registries JSR 93

- Jakarta XML RPC  JSR 101

- Jakarta Deployment JSR 88

- Jakarta Management JSR 77 note this was not optional or deprecated in Java EE 8

- Jakarta Enterprise Bean entity beans – Note this is old style CMP and BMP entity beans NOT JPA Entities

- Jakarta Enterprise Bean interoperability

- Jakarta Enterprise Bean 2.x and 1.x client view

- Jakarta Enterprise Web Services  JSR 109

 

Please vote by reply with +1, 0, -1 in accordance with the Eclipse Development Process.

 

Thanks


Steve

 

_______________________________________________

jakartaee-platform-dev mailing list


jakartaee-platform-dev@xxxxxxxxxxx

To change your delivery options, retrieve your password, or unsubscribe from this list, visit


https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

 

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

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


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

Back to the top