commercialhaskell / commercialhaskell/stack
Versioning strategy for unreleased stacks?
Open
type: enhancement
- Dominant language
- Haskell
- Stars
- 4.1k
- Forks
- 850
- Avg merge
- 10h 37m
- Merged PRs (30d)
- 4
Description
From https://stackoverflow.com/a/46289394/1164871 , apparently arch linux is packaging up master versions of stack. I suppose this is an ok thing to do. Master should always be in a fairly reasonable state, but not as guaranteed.
Anyway, main thing here is that it makes sense to me for the stack repo version to always differ from released version when under development. Could adopt a convention that odd minor version numbers are used for development, and releases have even minor version numbers.
@borsboom @snoyberg Thoughts?
Contributor guide
Assessment
This issue has not been assessed yet.