Sorry, I am a newbie and still learning (with a little bias from the
MPWG)...
So my vote must be corrected to the above.
Thanks for your clarification, Ivar
(and Amelia, who pointed this out too)!
Best,
Jan
Am 21.06.21 um 21:51 schrieb Ivar
Grimstad:
Thanks for your vote and justification for the
vote, Jan!
The iJUG seat in the WG does not make you a committer to
the platform project, so the flag should have been set to
false, but I am sure Scott verifies when he makes the final
count ;)
For information, there are 14 committers on the Jakarta
EE Platform project.
As having the iJUG seat in the Jakarta EE WG I hope I
set the committer flag correct...
Why voting like that:
Expecting a Jakarta Profile Release 10 in after Java SE
17 (LTS) is released, it is possible to vote for Opt3.
Being able to evolve the single platform specs and
bring them to a new profile was blocked by the namespace
changes in the past - now we should allow new language
features for the then current Java SE LTS version (17, and
not 11, which is from 2018-09-25).
Opt2 makes things a little more complicate for end
users to understand, but might circumvent some potential
issues with JPMS.
When Opt1 will win, we should go for Jakarta EE 11 soon
- but what would result in a short release cadence ;-)
Let's
try a contingent vote (https://en.wikipedia.org/wiki/Contingent_vote)
on the topic of what the Java SE requirements
are for the EE10 release. In a contingent voting
scheme you order the choices from most preferred
to least preferred. Anyone can vote, we can
decide how we want to prioritize/filter
non-committer votes once we have the data.
The
ballot will run until the midnight GMT on
June 21 so that we can discuss the results
on the June 22 platform meeting. That gives
a little less that two weeks.
We
have 3 options:
Opt1.
Java SE 11 as source/language level and
binary level for all API jars. Compatible
implementations are free to pass TCKs using
any Java SE version at 11 or higher.
Opt2.
Java SE 11 as source/language level and Java
SE 17 as binary level for all API jars.
Compatible implementations are free to pass
TCKs using any Java SE version at 17 or
higher.
Opt3.
Java SE 17 as source/language level and
binary level for all API jars. Compatible
implementations are free to pass TCKs using
any Java SE version at 17 or higher.
To
cast your vote, use the following JSON
syntax, for example, if I was favor Opt1
first, Opt3 second and Opt2 third:
"vote"
: {
"order":
["Opt1", "Opt3", "Opt2"],
"committer":
true
}
Set
the committer value based on whether you are
a current Jakarta-platform committer.
This e-mail and any files transmitted with it are for the
sole use of the intended recipient(s) and may contain
confidential and privileged information. If you are not
the intended recipient(s), please reply to the sender and
destroy all copies of the original message. Any
unauthorized review, use, disclosure, dissemination,
forwarding, printing or copying of this email, and/or any
action taken in reliance on the contents of this e-mail is
strictly prohibited and may be unlawful. Where permitted
by applicable law, this e-mail and other e-mail
communications sent to and from Cognizant e-mail addresses
may be monitored.