Re: [jakarta.ee-spec] [BALLOT] Plan Review for Jakarta JSON Binding 3.0

["Kevin Sutter" <sutter@xxxxxxxxxx>]

+0 (IBM)

I still might
change my vote before the deadline, but I'd like to understand what is
breaking to force a major version update (3.0).  And, what is the
potential impact to customers.  Updating the major version of a Spec
needs to be well thought out and documented.  The team probably does
have a good understand, but I just didn't see the justification in the
PR.  I have documented my request in the PR:
https://github.com/jakartaee/specifications/pull/348#issuecomment-827640232


---------------------------------------------------
Kevin Sutter 
STSM, Jakarta EE and MicroProfile architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter

Part-time schedule: Tue, Wed, Thu (off on Mon and Fri)



From:
       Ivar
Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
To:
       Jakarta
specification disccusions <jakarta.ee-spec@xxxxxxxxxxx>
Date:
       04/23/2021
02:21
Subject:
       [EXTERNAL]
[jakarta.ee-spec] [BALLOT] Plan Review for Jakarta JSON Binding 3.0
Sent
by:        "jakarta.ee-spec"
<jakarta.ee-spec-bounces@xxxxxxxxxxx>

---

Greetings Jakarta EE Specification Committee.

I need your vote to approve the Plan Review of Jakarta JSON Binding 3.0.

The JESP/EFSP states a Plan Review provides a means for the Specification
Project Team to present their Release Plan to the Project Leadership Chain,
the Specification Committee, and the community for feedback.  Also,
the JESP/EFSP requires a successful ballot of the Specification Committee
in order to ratify the Plan Review.

The relevant materials are available here:

https://github.com/jakartaee/specifications/pull/348
https://deploy-preview-348--jakartaee-specifications.netlify.app/specifications/jsonb/3.0/

Per the process, this will be a seven-day ballot, ending on Friday,
April 30, that requires a Super-majority positive vote of the Specification
Committee members (note that there is no veto). Community input is welcome,
but only votes cast by Specification Committee Representatives will be
counted.

The Specification Committee is composed of representatives of the Jakarta
EE Working Group Member Companies (Fujitsu, IBM, Oracle, Payara, Red Hat,
Tomitribe, and Primeton), along with individuals who represent the EE4J
PMC, Participant Members, and Committer Members.

Specification Committee representatives, your vote is hereby requested.
Please respond with +1 (positive), 0 (abstain), or -1 (reject).  Any
feedback that you can provide to support your vote will be appreciated.

Thanks

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation- Community. Code. Collaboration. _______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec