Develop a policy for how long we support Error Prone versions #882
Comments
Merged
msridhar
added a commit
that referenced
this issue
May 31, 2024
This PR drops support for running NullAway on a JDK 8 JVM. After it lands, running NullAway will require JDK 11 or above (like current versions of Error Prone). There are various cleanups that this change enables, but to keep the PR small, I tried to do close to the minimum. In particular: * I updated the minimum supported Error Prone version to 2.14.0, which is ~2 years old. Depending on what we decide about policy (see #882) we may want to bump this to an even more recent version. * Update our JDK 8 test tasks to instead just test building with the most recent supported Error Prone version but running on the oldest supported version. I tested locally that this does still detect binary compatibility issues. * Remove references to Java 11 in the jarinfer build files, as we now use that version everywhere. We will have to change the required CI job names before landing this. Will do other enabled cleanups in separate PRs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should develop a policy for how long we plan to support old Error Prone versions, and then somehow track in a more organized way what code cleanup can be done once we drop support for older versions (right now it's done in code comments but it can be hard to find).
The text was updated successfully, but these errors were encountered: