I saw this come by on Mastodon and Reddit, but I think it should also be linked here on Discourse:
15 Likes
Hello. Is there a separate Mastodon account for the Haskell blog?
I got it from the haskell.org account:
2 Likes
Oh geez, something I wrote has ended up on reddit and mastodon? Hopefully I did not embarrass the community.
Maybe I finally need to join mastodon to be part of the conversation there as well. There are so many communication mediums.
4 Likes
I’m really thankful for the work this group does. Having a body that ensures stability issues are brought up and represented well is a great benefit to the Haskell community and ecosystem.
5 Likes
No but there’s an RSS feed
2 Likes
@telser and the SWG are doing amazing work! According to my breakage inventory, GHC 9.12 was the least-breaking release in a long time, maybe a decade, or more?
[If I’ve missed anything off the inventory please let me know!]
4 Likes
Apart from the SWG, this is also largely due to:
- GHC steering committee and their new stability principles
- CLC being rather strict about breaking changes in base
- GHC HQ developing awareness about this issue
What I’d like to see from the SWG is:
- data/statistics/experience reports that show the need for stability (or the impact the lack of stability has)
- Maintainership standards · Issue #7 · haskellfoundation/stability · GitHub
- exploring ways on how to achieve stability as a maintainer (nuances of PVP, models of package maintainership, the role of hackage, are build systems an interface, what about cabal flags, etc.)
As an example… when we think of PVP or API, we think about Haskell code. What about cli interfaces? They are covered by neither. Cabal v1 vs v2 is an interesting data point that probably was the single largest breaking change of cli tools in Haskell.
7 Likes