Internals: deprecation policy
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 252
- Forks
- 98
- Avg merge
- 7h 12m
- Merged PRs (30d)
- 4
Description
Description
We need to formalize/revise the current deprecation policy, which doesn't exist in writing yet.
References:
- https://www.doctrine-project.org/policies/deprecation.html
- https://www.drupal.org/about/core/policies/core-change-policies/how-to-deprecate
- https://discourse.laminas.dev/t/deprecation-policy-trigger-error-vs-deprecated/2435
- https://docs.djangoproject.com/en/6.0/internals/release-process/#deprecation-policy
- https://symfony.com/doc/current/contributing/code/conventions.html#deprecating-code
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 the existing documentation structure and the linked deprecation policies from Doctrine, Drupal, Laminas, Django, and Symfony. The issue names no target file or current policy text, so first identify where the policy belongs and which decisions need agreement. Done means a formal, written deprecation policy is added and its scope is accepted by the project.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100