Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] BALLOT: Approval to release Jakarta MVC 2.0

+1 (IBM) with a caveat...

I found a couple of minor items while reviewing this MVC 2.0 Release:

The main item that is still outstanding is that the license link at the bottom of the javadoc pages gets a 404 error.  To correct this, new staging artifacts would need to be posted.  Since nobody else has found this error yet with multiple +1's already logged, I'm okay with Ivar restaging the MVC 2.0 artifacts with the corrected license link (and version title).  Otherwise, Ivar would have to go forward with what is already posted and then do a separate 2.0.1 release to correct the javadoc.  That seems like overkill.  But, let's see what others think...

Kevin Sutter
STSM, Jakarta EE and MicroProfile architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    

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

From:        Scott Stark <starksm64@xxxxxxxxx>
To:        Jakarta specification disccusions <>
Date:        12/03/2020 19:17
Subject:        [EXTERNAL] [] BALLOT: Approval to release Jakarta MVC 2.0
Sent by:

Greetings Jakarta EE Specification Committee.

I need your vote to approve and ratify the release of Jakarta MVC 2.0 as a standalone release.

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 fourteen day ballot, ending on Dec 17 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 …_______________________________________________ mailing list
To unsubscribe from this list, visit

Back to the top