Define policy for deprecating and dropping support of legacy versions of Java
Problem to solve
Historically, our timeline for deprecating older versions of Java, and its package manager(s) maven/gradle
has always been inconsistent. We have deprecated language and package manager versions on a case by case basis, and commonly did so when the maintenance cost was too high. This issue aims to solve that by defining and agreeing to a deprecation and removal timeline for older Java and maven/gradle
releases. This makes our support timeline predictable, and proactively manages our maintenance load.
- Affects dependency scanning which indirectly affects license scanning
- Impacts the dependency scanning supported language and package managers docs
Further details
Relates to https://gitlab.com/gitlab-com/gitlab-OKRs/-/work_items/2953+
Proposal
TODO
Who can address the issue
Other links/references
Edited by Oscar Tovar