haskell / haskell/pvp

condition 2 (Non-breaking changes) examples are too limited

Open
#41 11 comments 0 reactions 0 assignees View on GitHub
Dominant language
CSS
Stars
40
Forks
24
PR merge metrics
No merged PRs in 30d

Description

> 3. Other changes. Otherwise, e.g. if change consist only of corrected documentation, non-visible change to allow different dependency range etc. A.B.C MAY remain the same (other version components may change).

Surely if I do a small tweak that improves output formatting say, that would also come under this, right?

Only mentioning documentation and dependency range changes here seems too small a class of examples to me, no?

Contributor guide

Open the contributing guide

Research direction

Start with the quoted “Other changes” wording in Condition 2 and review the surrounding Haskell Package Version Policy specification. Determine how output-formatting changes should be represented among the non-breaking examples, then confirm the revised examples clearly cover the intended class without changing the policy’s meaning.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.