Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] BALLOT: Approval of the plan for Jakarta NoSQL 1.0

+1 as Plan Review, for Oracle with the following commentary:

We are excited to see the development of this technology in Jakarta EE. We want to encourage further development of this technology. But as a planning statement, I am at a bit at a loss to understand that plan.

Several suggestions have been provided as commentary in the ballot, but I suspect that's probably not the best way to provide this feedback, nor to see that these suggestions are folded into the development roadmap. Perhaps these could be addressed in a future Update review

Regardless, in that vein (and some of these may seem obvious but these should be clearly stated, in my opinion) ...

Is this proposed to become part of the Jakarta EE platform?

If so,

  • Is there a particular Jakarta EE release target?
  • Has this been discussed with any members of the platform committer team? 
  • What resources would be available to fold this into the platform Spec?
  • Do the collective members of these groups agree on such a plan?
  • Is there a compatible implementation target platform/product for that effort?

Otherwise, what is the evolutionary roadmap that makes sense for this technology?

I'd encourage the committer team to, at least take a SWAG at future release target dates. Probably those could be added to the project "governance pages" (the last update here was 0.1.0 release review in 2019). If you'd prefer to just put a Plan page in the main project repository, that's probably a good enough start.

It is clear that lots of work is being invested in this technology and we are very appreciative and want to continue to encourage this work. Let's try to make sure the Jakarta / EE4J community are supporting this evolution so that it can launch with maximum impact!


-- Ed Bratt

On 10/4/2020 10:27 PM, Ivar Grimstad wrote:

Greetings Jakarta EE Specification Committee.

I need your vote to approve the plan for Jakarta NoSQL 1.0.

The JESP/EFSP requires a successful ballot of the Specification Committee in order to ratify the products of this release as a Final Specification (as that term is defined in the EFSP).

The relevant materials are available here:

Per the process, this will be a seven day ballot, ending on October 12, 2020 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, Inc.

Community. Code. Collaboration. 

Join us at our virtual event:
EclipseCon 2020 - October 20-22

_______________________________________________ mailing list
To unsubscribe from this list, visit;!!GqivPVa7Brio!LbAk2PuorgtsaVY3hCNa-oKJrWQC35nFe15L6Es2jOsjNIbvCJSk45CZl1ZzOyA$ 

Back to the top