Add regret.policies.SemVer
Open
- Dominant language
- Python
- Stars
- 15
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
This deprecation policy uses SemVer based deprecation periods. A period of time may be used in addition (#12), but otherwise, errors shown via #14 / #1 should be fired after e.g. a major version has rolled over.
Contributor guide
Research direction
Start by reading the existing regret.policies module and the referenced issues #12, #14, and #1 to understand how deprecation policies and errors are represented. Implement the SemVer policy so deprecation errors fire after the specified major-version rollover, with completion defined by the behavior described in this issue and the related discussions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100