Community survey: Long-Term Support policy for cabal-install releases
- Dominant language
- Haskell
- Stars
- 1.7k
- Forks
- 750
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 28
Description
The cabal development community is thinking about setting a Long-Term Support policy for `cabal-install`. In order to inform our decision, we want people to tell a bit about how they use the toolchain.
A point of definition:
* "Old" cabal-install releases are the ones older than "recommended" on ghcup. Currently, ghcup recommends `3.10.3.0`.
* "Old" GHC versions are the ones that are more than 3 releases old:
* GHC 9.10: new
* GHC 9.8: not-so-new
* GHC 9.6: reasonably stable
* GHC 9.4 and older: old.
* Are you interested in an LTS release of `cabal-install`?
* For professionals: Would this be beneficial for adoption in your organisation?
* Do users usually stick with a `cabal-install` release
* Do users stick around with old versions of GHC and for how many years?
* Are old `cabal-install` versions used with old and/or recent versions of GHC?
This survey is non-binding, and is part of a larger effort from the Cabal team to better know our user base. Please do not start conversations in this thread. The Haskell Discourse forum is more appropriate.
Contributor guide
Research direction
No source file or test is named because this issue is a non-binding community survey about a Long-Term Support policy for cabal-install. Read the definitions and questions in the issue, then use the Haskell Discourse forum for responses, as requested. Done means contributing relevant user or organizational experience rather than changing the repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100