[jakartaee-platform-dev] [BALLOT COMPLETE] Include Query in Platform and

[Jared Anderson <jhanders@xxxxxxxxxx>]

Yes it did pass.  I hadn't gotten to sending the email yet.  Here it is though.

I declare this ballot complete and approved.  The summary of the votes is below.

Committer	Vote
Ivar Grimstad	+1
Ed Bratt	+1
Kenji Kazumura	+1
Scott Marlow	+1
Emily Jiang	+1
James Perkins	+1
Jared Anderson	+1
Non-binding votes	Vote
Lenny Primak	+1
Bernd Müller	+1
Michael Redlich	+1
Angelo Rubini	+1

Jared Anderson
Senior Software Engineer
WebSphere Performance Engineering

Websphere Jakarta Development Lead

Internet Address: jhanders@xxxxxxxxxx

---

From: Otavio Santana <otaviopolianasantana@xxxxxxxxx>
Sent: Wednesday, October 15, 2025 7:26 AM
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: Jared Anderson <jhanders@xxxxxxxxxx>
Subject: [EXTERNAL] Re: [jakartaee-platform-dev] BALLOT to include Query in Platform and Web Profile 12

 

Hello everyone, the Jakarta Query has passed, right? On Mon, Sep 29, 2025 at 9: 25 PM Jared Anderson via jakartaee-platform-dev <jakartaee-platform-dev@ eclipse. org> wrote: This email indicates the start of a ballot for inclusion of Jakarta

Hello everyone, the Jakarta Query has passed, right?

On Mon, Sep 29, 2025 at 9:25 PM Jared Anderson via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:

This email indicates the start of a ballot for inclusion of Jakarta Query into the Jakarta EE Platform and Web Profile 12.

To summarize discussions from the platform meetings over the last few weeks:

• The Query specification is in a very good state to be able to make an informed decision in this vote.  You can see details about the specification using the README and a snapshot version of the specification.
• The Query specification representatives on the platform meeting indicated that they believe they only have 1 to 3 months of work remaining which fits well with the Jakarta EE 12 schedule.
• The Data, NoSQL and Persistence specifications need a decision on whether Query will be part of the platform in order to adjust their specifications to reference the Query specification.
• Ratifying of the Query specification will require both Data and Persistence to include tests in their TCKs to test both the Core and Extended Query models respectively.  The ratification of those two specifications will allow for the Query specification to ratify.  (Jakarta NoSQL will also need to have TCK tests for the Core model.)  This test approach is similar to what is done for the Jakarta Interceptors and Jakarta Annotations specifications.
• If this vote passes and the Query specification for some reason cannot meet the Jakarta EE 12 schedule, it will not be part of the EE 12 release and the dependent specifications will need to adjust.  This is business as usual for any component specification version update.

Vote +1 (positive), 0 (abstain), or -1 (reject) on this BALLOT to indicate your preference regarding whether or not to include the Query specification in the Web profile, in addition to the Platform. This vote will be counted by simple majority of Platform Project committers as listed in https://projects.eclipse.org/projects/ee4j.jakartaee-platform/who (note that there is no veto).  Any feedback that you can provide to support your vote will be appreciated.  This will be a fourteen-day ballot, ending on Monday, October 13, 2025 or when all committers have voted, whichever comes first.

Non-committers are encouraged to vote as a measure of community sentiment.

Jared Anderson
Senior Software Engineer
WebSphere Performance Engineering

Websphere Jakarta Development Lead

Internet Address: jhanders@xxxxxxxxxx

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

--

Thanks a lot,

Twitter | Linkedin | Youtube