Hi Quan
+1 on the principle.
However I have a few remarks:
1. Please be precise on James versions:
- Java 21 will be used by Apache James for versions 3.9.0 onward
- Java 11 will be used by Apache James for versions 3.7.x and 3.8.x.
No backport of the Java 21 switch is planned.
2. Votes follow a more formal procedure within the ASF, and voting rules
shall be clearly stated (voting time, voting threshold) cf
https://www.apache.org/foundation/voting.html
In practice:
- I propose the wording "lazy consensus"
- for code changes we may remind that the vote may be vetoed
- Provide an explicit voting time range specifying starting date and
time and ending date.
In practice a minimum of 3 days is recommended.
Regards
Benoit
On 06/02/2024 04:36, Quan tran hong wrote:
Hi everyone,
Following the Jira ticket
<https://issues.apache.org/jira/projects/JAMES/issues/JAMES-3961?filter=allissues>
and the previous mailing list discussion
<https://www.mail-archive.com/server-user@james.apache.org/msg16892.html>
regarding Java 21 adoption for James, I and Benoit put together an effort
to successfully get a green build on the Java 21 adoption PR
<https://github.com/apache/james-project/pull/1963>.
The idea is to have James migrated to Java 21 with minimal changes first,
and after that, we can leverage new Java features gradually.
Because this is a big change for James, James's community review, remarks,
and opinions on merging the Java 21 PR should be needed.
It would be good if the community could spend some time reviewing the PR,
or just upvote/downvote directly on this mail thread.
Thanks for reading.
Best regards,
Quan
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
