Just to support what Kevin is saying.
These current votes are ONLY for the platform project to scope and put together the proposed release plan. The release plan will then be formally
voted on and approved by the specification committee as described by the EFSP
https://www.eclipse.org/projects/efsp/#efsp-plans . The rules for approval at the formal spec committee vote are;
A Release Plan must be approved by a Super-majority of the Specification Committee.
We are following the EDP
https://www.eclipse.org/projects/dev_process/ for these informal votes “Committers are required
to track, participate in, and vote on, relevant discussions in their associated Projects. There are three voting responses:
+1 (yes),
-1 (no, or veto), and
0 (abstain).”
So these informal votes are limited to project committers and is not a majority decision a single -1 will pull the vote and we will discuss the proposal
again.
My intention is to use these votes, combined with decisions documented on the calls to build up the draft release plan content by putting approved
items into the plan just to provide a level of decision audit.
Sorry for any confusion.
Steve
From: jakartaee-platform-dev-bounces@xxxxxxxxxxx <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Kevin Sutter
Sent: 20 November 2019 21:54
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] VOTE: Specifications to PruneinJakarta EE 9
Correct, any formal voting will be taking place by either the Steering Committee or the Spec Committee. And, those votes all follow the more formal voting requirements of 1
vote per member organization.
The processing and analyzing of these informal votes will be done by the Jakarta EE 9 release leads (yours truly and Steve Millidge).
---------------------------------------------------
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 15:30
Subject: [EXTERNAL] Re: [jakartaee-platform-dev] VOTE: Specifications to PruneinJakarta EE 9
Sent by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
So the formal vote is then by the Spec Committee.
Was a way of properly processing and analyzing all those votes (currently by mail) also discussed?
Werner
Sent from
Mailfor Windows 10
From:
Kevin Sutter
Sent: Wednesday, November 20, 2019 22:23
To: jakartaee-platform developer discussions
Subject: Re: [jakartaee-platform-dev] VOTE: Specifications to PruneinJakarta EE 9
Remember, we are only talking about the content and planning for Jakarta EE 9. This is just get a reading from the participants. These are not binding
votes, per se. These are informal votes to get a reading from the Platform committers.
And, this was discussed. I posted the idea to the mailing list. Then, we discussed it at our Platform Dev call. And, I have pointed at the minutes. As was stated, we're going to go with this each committer gets a vote until an issue arises with that process.
---------------------------------------------------
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: Amelia Eiras <aeiras@xxxxxxxxxxxxx>
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date: 11/20/2019 15:08
Subject: [EXTERNAL] Re: [jakartaee-platform-dev] VOTE: Specifications to Prune inJakarta EE 9
Sent by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
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.
Amelia Eiras
twitter.com/ameliaeiras
Tribe:http://tomitribe.com https://tribestream.io
OSS: http://microprofile.io
https://jakarta.ee
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_______________________________________________
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
