issues
search
haskell
/
pvp
Haskell Package Version Policy (PVP)
http://pvp.haskell.org/
38
stars
25
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Fix #39 (Link to logo is dead)
#61
BinderDavid
closed
1 month ago
3
Add compatibility with GHC 9.X and test in CI
#60
BinderDavid
closed
1 month ago
2
Improve grammar
#59
tomjaguarpaw
closed
5 months ago
1
Remove point 7 about deprecation
#58
hasufell
closed
9 months ago
4
Clarify role of the FAQ
#57
hasufell
opened
10 months ago
0
Provide guidance on non-enumerated changes
#56
gbaz
opened
11 months ago
4
What is the goal of the PVP?
#55
michaelpj
opened
11 months ago
21
[RFC] Make PVP ecosystem/language agnostic
#54
hasufell
closed
11 months ago
24
Make clear .Internal convention does not adhere to the spec
#53
hasufell
closed
1 year ago
20
Make clear the tree doesn't precisely represent the spec
#52
hasufell
closed
1 year ago
16
Drop the requirement of specifying upper bounds
#51
hasufell
opened
1 year ago
31
Add a FAQ entry about multiple public libraries
#50
michaelpj
closed
1 year ago
12
Clarify bumping policy for bug fixes
#49
andreasabel
opened
1 year ago
4
Fix #47: remove outdated tools
#48
andreasabel
closed
1 year ago
6
Tools section points to outdated tools, so remove or update it
#47
andreasabel
closed
1 year ago
0
Formalize ".Internal" module convention
#46
bgamari
closed
1 year ago
40
Fix small formatting wibble
#45
bgamari
closed
1 year ago
0
The PVP should include advice about SafeHaskell
#44
andreasabel
closed
1 year ago
2
Do you need help with pvp.haskell.org?
#43
andreasabel
opened
1 year ago
2
(non-enforced) section on prerelease versions?
#42
hasufell
opened
2 years ago
3
condition 2 (Non-breaking changes) examples are too limited
#41
juhp
opened
2 years ago
11
Clarify rule two
#40
Taneb
opened
2 years ago
2
Missing logo
#39
visortelle
closed
1 month ago
0
Update PVP specification to mention non-leading zeros
#38
psilospore
closed
2 years ago
27
Hav k
#37
ghost
closed
2 years ago
2
Remove the "2.0.1.0 > 2.0.1" example, or clarify that this is bad
#36
andreasabel
opened
2 years ago
4
## Overview
#35
ghost
closed
2 years ago
1
Block all
#34
ghost
closed
2 years ago
2
Does removing a Cabal flag constitute a breaking change?
#33
sjakobi
opened
3 years ago
3
Fix typo in 'Leaking instances' example code
#32
chuahou
closed
2 years ago
0
new version number suggestions seem wrong?
#31
benjaminselfridge
opened
4 years ago
6
Mention changing definitons of functions or values as Breaking change
#30
phadej
closed
3 years ago
7
FAQ should mention x-uncurated
#29
massysett
opened
4 years ago
0
Translations?
#28
unhappychoice
closed
3 years ago
1
Fix typos, remove superfluous commas and improve wording in pvp-faq.md
#27
mattaudesse
closed
5 years ago
0
Typo fix: similiar -> similar
#26
Wizek
closed
6 years ago
1
Decision tree diagram recommends misleading version numbers
#25
gwils
closed
6 years ago
2
Is it PVP conform if a package leaks orphan instances or not depending on the versions of its transitive dependencies?
#24
sol
opened
6 years ago
1
Is the PVP transitive?
#23
sol
opened
6 years ago
1
Does not address Safe Haskell related breakage
#22
snoyberg
opened
6 years ago
4
Trying to reach community consensus by focusing on the things that are uncontroversial
#21
sol
closed
6 years ago
7
Change diagram to suggest more common numbering progression
#20
xkollar
closed
6 years ago
4
Version the PVP spec itself?
#19
tfausak
closed
5 years ago
6
Revise deprecation clause (close #12)
#18
sol
closed
5 years ago
9
Instructions how to build unclear
#17
wereHamster
closed
7 years ago
3
Typo: succesfull -> successful
#16
osa1
closed
7 years ago
1
Give guidance about patch releases?
#15
tfausak
opened
7 years ago
5
Require smaller components to reset?
#14
tfausak
opened
7 years ago
3
Prevent non-contiguous version ranges?
#13
tfausak
closed
3 years ago
8
Revise deprecation clause
#12
hvr
closed
9 months ago
13
Next