Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Roadmap: Move to Java 17 as a baseline this year (2022) #3320

Closed
shemnon opened this issue Jan 24, 2022 · 3 comments
Closed

Roadmap: Move to Java 17 as a baseline this year (2022) #3320

shemnon opened this issue Jan 24, 2022 · 3 comments
Assignees
@usmansaleem
Labels
TeamGroot GH issues worked on by Groot Team

Comments

@shemnon
Copy link
Contributor

shemnon commented Jan 24, 2022

Description

As a developer and end user I want the baseline Java version updated from 11 to 17 so that I can have access to higher performance Java features such as Records, expression switch, and a compiler that produces Java bytecode tuned for faster VMs.

Acceptance Criteria

  • Besu builds out of the box with Java 17 and all up-to-date versions newer than 17
  • Besu does not build on Java 11 through Java 16. This is detected in the build script early and the build script produces a meaningful error.
  • For X quarterly releases (one full and one partial?) the release notes warn about the migration
  • After the first release with the warning The build script produces a warning that Besu will be migrating to Java 17 as the base
@frankisawesome frankisawesome mentioned this issue Jan 25, 2022
Merged
@non-fungible-nelson non-fungible-nelson added the icebox items that need more consideration, time, or can wait label May 24, 2022
@iamhsk iamhsk added the TeamChupa GH issues worked on by Chupacabara Team label Jul 14, 2022
@jflo jflo removed icebox items that need more consideration, time, or can wait TeamChupa GH issues worked on by Chupacabara Team labels Nov 1, 2022
@macfarla
Copy link
Contributor

Related - #4774

@macfarla
Copy link
Contributor

WIP PR #4532
current build failures

@macfarla
Copy link
Contributor

may be a clue for the TLS failing test here #4622

@bgravenorst bgravenorst mentioned this issue Jan 16, 2023
Closed
This was referenced Jan 23, 2023
Merged
Closed
@usmansaleem usmansaleem self-assigned this Jan 29, 2023
@usmansaleem usmansaleem added TeamGroot GH issues worked on by Groot Team doc-change-required Indicates an issue or PR that requires doc to be updated labels Jan 29, 2023
@jframe jframe closed this as completed Feb 5, 2023
@bgravenorst bgravenorst removed the doc-change-required Indicates an issue or PR that requires doc to be updated label Feb 15, 2023
@lucassaldanha lucassaldanha mentioned this issue Apr 19, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@usmansaleem usmansaleem

Labels
TeamGroot GH issues worked on by Groot Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@shemnon @jflo @usmansaleem @jframe @iamhsk @macfarla @bgravenorst @non-fungible-nelson