haskell / haskell/cabal

[meta] Should for-ghc-only releases take up major release numbers?

Open
#10,334 2 comments 1 reaction 0 assignees View on GitHub
re: devx
Dominant language
Haskell
Stars
1.7k
Forks
750
Avg merge
4d 3h
Merged PRs (30d)
28

Description

I am wondering if a better approach, given that these releases are not intended for public use but only for ghc, is to expand our use of devel release numbers: assuming that it's too late to fix this for 3.14, then

- 3.15.0.0 is the first devel version
- 3.15.1.0 would be the first for-ghc release
- 3.15.2.0 would be for continued development after the first for-ghc release
- if needed, we could repeat this with 3.15.3.0/3.15.4.0 and so on.

This way we don't confuse our release numbers, which currently are on course for us to _from a public release standpoint_ skip from 3.12.1.0 to 3.16.0.0.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.