Develop a policy for how long we support Error Prone versions
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.1k
- Forks
- 370
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 68
Description
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).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the project currently supports Error Prone versions and where code-cleanup notes are recorded in comments. Define a support-period policy and an organized way to track cleanup opportunities after older versions are dropped; done means both the policy and tracking approach are documented and usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100