Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refine GHC deprecation policy #3438

Merged
merged 8 commits into from
Jun 15, 2024
Merged

Refine GHC deprecation policy #3438

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
93b1219
Refine GHC deprecation policy
hasufell Jan 4, 2023
4e39448
Update docs/support/ghc-version-support.md
hasufell Jan 19, 2023
9b995aa
Update docs/support/ghc-version-support.md
hasufell Jan 19, 2023
a917e54
Reword to support status, as this is mentioned above
fendor Jun 14, 2024
9633326
Include ghcup recommended version in support discussion
fendor Jun 15, 2024
37248df
Merge branch 'master' into refine-policy
soulomoon Jun 15, 2024
a4907ff
reword
soulomoon Jun 15, 2024
bf91737
Reword
michaelpj Jun 15, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update docs/support/ghc-version-support.md 
Co-authored-by: Michael Peyton Jones <me@michaelpj.com>
  • Loading branch information
@hasufell @michaelpj @fendor
2 people authored and fendor committed Jun 14, 2024
commit 9b995aac0924464218da55ca4a2a08d1f9836ef6
2 changes: 1 addition & 1 deletion docs/support/ghc-version-support.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,7 @@ To establish and apply the policy we also take into account:
- The reliability of different ghc versions on the major operating systems (Linux, Windows, MacOS)
- The [Haskell Survey results](https://taylor.fausak.me/2022/11/18/haskell-survey-results/#s2q4)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think these three points are the interesting ones. I'd move them into the next section where they're used.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also don't understand this suggestion. This is the section about Ecosystem factors. Why would that go into the next section, which explains the process of supporting older GHCs?


### Supporting a GHC version beyond its shelf life
### Supporting a GHC version beyond normal deprecation time

In cases where the base policy demands a deprecation, but ecosystem factors
suggest that it's still widely used (e.g. last [Haskell Survey results](https://taylor.fausak.me/2022/11/18/haskell-survey-results/#s2q4)), the deprecation should be suspended for the next release and the situation be re-evaluated for the release after that.
Expand Down