Proposal: Replace obsolete with deprecated
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 787
- Forks
- 216
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 6
Description
### What information was incorrect, unhelpful, or incomplete?
see https://github.com/mdn/data/pull/797#discussion_r1860535126
mdn/content and mdn/browser-compat-data has already no longer use obsolete anymore, and replace it with deprecated
### What did you expect to see?
same as above
### Do you have any supporting links, references, or citations?
https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Experimental_deprecated_obsolete, explains why obsolete should not to be used and deprecated should be used
### Do you have anything more you want to share?
_No response_
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
Search the mdn/data repository for `obsolete`, beginning with the linked pull-request discussion and the MDN guidance on experimental, deprecated, and obsolete features. Identify the data entries in scope and replace the applicable terminology with `deprecated`; done means the intended data no longer uses `obsolete`, consistent with mdn/content and mdn/browser-compat-data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100