Clarify bumping policy for bug fixes
- Dominant language
- CSS
- Stars
- 40
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
This question comes from:
- https://github.com/haskell/alex/issues/227
In this situation, position information generated by Alex < 3.2.7 had a bug that was fixed in 3.2.7.
However, `cabal` had workarounds for the bug which broke after the bug was fixed.
The current PVP does not talk about behavioral changes of a definition, only about changing its _type_.
I would have thought a bugfix is a patch release (fourth digit bump).
From the current example (workaround breaking) one could also argue for a major version bump for bug fixes that change the output of a function (rather than just making it more defined).
What is your take on this?
The PVP should be extended to mention bug fixes in the appropriate place.
Contributor guide
Research direction
Start by reading the current PVP text on version changes and the referenced Alex issue 227, including the cabal workaround discussion. Done means the policy explicitly explains how bug fixes that change observable behavior should affect version bumps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100