search

haskell / pvp

Haskell Package Version Policy (PVP)
http://pvp.haskell.org/
38 stars 25 forks source link

Remove point 7 about deprecation #58

Closed hasufell closed 12 months ago

hasufell commented 12 months ago

Related: https://github.com/ghc-proposals/ghc-proposals/pull/625

  1. Deprecation. Deprecated entities (via a DEPRECATED pragma) SHOULD be counted as removed for the purposes of upgrading the API, because packages that use -Werror will be broken by the deprecation. In other words the new A.B SHOULD be greater than the previous A.B.

This is a very unreasonable suggestion and in fact would imply two major version bumps for a deprecation.

hasufell commented 12 months ago

In fact, given that deprecation warnings have bad mechanics when it comes to module re-exports, you may end up with 3 major version bumps to not break -Werror: https://github.com/haskell/filepath/issues/209

phadej commented 12 months ago

Duplicate of https://github.com/haskell/pvp/issues/12

hasufell commented 12 months ago

Excellent. Given this has been long in the queue, can we vote on this @Bodigrim ?

gbaz commented 12 months ago

note that its already in the draft of pvp 1.1. so i guess this would encourage us to try to look at pvp 1.1 and make sure we understand the differences to 1.0, then roll it out on an actual timeline.