Clarify JLBP-13. It's not to meant to delete deprecated features in your library

Open Beginner friendly
#1,896 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
62/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
documentation

Research direction

Start by locating the documentation that defines JLBP-13 and compare its wording with the distinction in this issue. Clarify that the rule concerns removing deprecated-feature usage from project code, not deleting deprecated features from a library; done means the guidance unambiguously communicates that scope.

Written by the indexing model from the issue text.

Description

best practices

JLBP-13 Remove references to deprecated features in dependencies at the first opportunity

This is meant to stop using deprecated features in your code. It's not for library devs to delete deprecated features quickly.

Dominant language
Java
Stars
163
Forks
81
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GoogleCloudPlatform/cloud-opensource-java

All issues in GoogleCloudPlatform/cloud-opensource-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.