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.

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

Spike what is left to do to fully move to Java 21 #27864

Closed
spbolton opened this issue Mar 6, 2024 · 1 comment
Closed

Spike what is left to do to fully move to Java 21 #27864

spbolton opened this issue Mar 6, 2024 · 1 comment

Comments

@spbolton
Copy link
Contributor

spbolton commented Mar 6, 2024

Parent Issue

No response

Task

A one day spike work, The aim to create a series of estimated tasks in an epic that cover any remaining work that would be required to fully migrate over to Java 21. Currently we are able to build but not fully test with Java 21 and particular test features like Mokito and Powermock may be causing issues. We should outline the minimum required to switch over, and then any follow up work that might be required e.g. changes to make use of new features.
This task follows on from initial work by Will in #27766 and #27767

Proposed Objective

Application Performance

Proposed Priority

Priority 3 - Average

Acceptance Criteria

1 Day of testing the current migrated branch to find any issues ant confirm if there are problems with upgrading and dependencies that may need to be updated.

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

@nollymar
Copy link
Contributor

Two new epics were created after identifying the remaining work:
#27993
#27996

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants