Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [bean-validation-dev] [jakarta.ee-spec] [BALLOT-DISCUSS] Plan Review of Jakarta EE Validation 4.0
Hi Ed,

I've copied the BVAL issues targeted for EE 12 to GH issues. The relevant issue to review and migrate the remaining BVAL issues is https://github.com/jakartaee/validation/issues/227.

Regarding the beanvalidation.org site and issue https://github.com/jakartaee/validation/issues/220, you mentioned, we are effectively within option (2) "Transfer ownership (push access) to people working on Jakarta Validation," as I have the push access and have already updated the site to mention Jakarta Validation 3.1. I wouldn't include the work on the site as part of the plan for the EE 12, as it does not directly affect the specification, and we can work on the site at a different pace. 

Have a nice day,
Marko


On Tue, 29 Apr 2025 at 19:39, Ed Bratt via bean-validation-dev <bean-validation-dev@xxxxxxxxxxx> wrote:

It is a bit concerning to me that the issues referenced in this Specification Proposal are on an archived issue tracker and cannot be edited. These include

I notice there is an open issue 'beanvalidation.org is no longer maintained' -- which may have a relationship to my concern.

Would the specification committer team be willing to migrate these issues to the Jakarta Validation GH repository issue tracker? I have filed https://github.com/jakartaee/validation/issues/256 to capture my suggestion.

I'd prefer that the committer team invest a modicum of its energy in creating a new site, hosted in Eclipse or GitHub pages and migrating any issues that are still relevant and I'd rather see this detailed in the proposal for EE 12.

-- Ed

On 4/25/2025 1:36 AM, Ivar Grimstad via jakarta.ee-spec wrote:

Greetings Jakarta EE Specification Committee,

I request your vote to approve and ratify the plan for the Jakarta Validation 4.0 specification.

The JESP/EFSP requires a successful ballot of the Specification Committee in order to approve the plan of this release (as defined in the EFSP).

The relevant materials are available here:

Per the process, this will be a seven-day ballot, ending on Friday, May 2, 2025, 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, Tomitribe, Primeton, and Shandong Cvicse Middleware Co.), 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://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec__;!!ACWV5N9M2RV99hQ!Je2-jhEvWGW9K2ybdiSwHLHjncqqE3reXC8b6RYPoyvoX-ph6Poj_u7wXk8YH9xkhXcRuU9jKqOQ95zm63ivwOkU2z0$
_______________________________________________
bean-validation-dev mailing list
bean-validation-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/bean-validation-dev

Back to the top