Latest revision as of 10:16, 26 February 2024

Haskell GHC 9.6 and Stackage LTS 22

Summary

Update the GHC Haskell compiler from major version 9.4 to 9.6 and Haskell packages from Stackage LTS 21 to LTS 22 versions.

Owner

Name: Jens Petersen
Email: <petersen@redhat.com>

Current status

Targeted release: Fedora Linux 41
Last updated: 2024-02-26
Announced
Discussion thread
FESCo issue: #3133
Tracker bug: #2258070
Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

For Fedora 40, the main GHC Haskell compiler package will be updated from version 9.4.5 to the latest stable 9.6.4 or newer bugfix release (rebasing the ghc package with the ghc9.6 package). Along with this, Haskell packages in Stackage (the stable Haskell source package distribution) will be updated from the versions in LTS 21 to latest LTS 22 release. Haskell packages not in Stackage will be updated to the latest appropriate version in the upstream Hackage package repository.

Feedback

Benefit to Fedora

Fedora users will have the latest stable Haskell compiler release, package tools, and current Haskell packages from latest Stackage LTS.

GHC 9.6.4 is the latest current stable version of GHC with various enhancements and fixes (see the release notes linked in the Documentation section for more details about new features and improvements in 9.6).

Scope

Proposal owners:
- update rawhide ghc9.4 is build against itself
- rebase ghc to 9.6.4
- refresh packagings with the latest cabal-rpm release if needed
- update packages to latest Stackage LTS 22 versions using cabal-rpm
- build all the packages in a Koji sidetag repo in dependency order using fbrnch
- push the sidetag through Bodhi to rawhide
- deal with obsoleting ghc9.6 if needed

Other developers: no actions should be needed

Release engineering: #Releng issue number

Policies and guidelines: N/A (not needed for this Change)

Trademark approval: N/A (not needed for this Change)

Alignment with Community Initiatives: N/A

Upgrade/compatibility impact

Any dropped packages will have obsoletes added. Otherwise there should not be any direct upgrade impact.

Users' Haskell projects will get built with ghc-9.6 when they next build them and might need some minor code tweaks (see the release notes linked below).

How To Test

install ghc and cabal-install
install pandoc, ShellCheck, ghcid, git-annex, hadolint, stack, xmonad, Agda
install ghc-*-devel or ghc-*-prof or ghc-*-doc
cabal-rpm builddep <favouritepackage>; cabal install <favouritepackage>
install ghc8.10, ghc9.0, ghc9.2, ghc9.4, or ghc*devel
test upgrades of F39 Haskell packages to F40

User Experience

Users will have the most recent stable major version of ghc and Haskell libraries and tools available to them. This makes it easier to build the latest versions of Haskell projects.

In particular cabal-install will also be updated from 3.8 to 3.10, pandoc will be updated to 3.1, and stack to 2.13.

Dependencies

Contingency Plan

Contingency mechanism:
- Change owner will drop the new builds and revert dist-git back to the versions in F39
Contingency deadline: Beta Freeze
Blocks release? No

Documentation

https://downloads.haskell.org/~ghc/9.6.4/docs/html/users_guide/9.6.1-notes.html

Release Notes

@@ Line 1: / Line 1: @@
 = Haskell GHC 9.6 and Stackage LTS 22 =
-{{Change_Proposal_Banner}}
 == Summary ==
-Update the GHC Haskell compiler from major version 9.4 to 9.6, and Haskell packages will be updated from Stackage LTS 21 to LTS 22 versions.
+Update the GHC Haskell compiler from major version 9.4 to 9.6 and Haskell packages from Stackage LTS 21 to LTS 22 versions.
 == Owner ==
@@ Line 20: / Line 19: @@
 == Current status ==
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF41]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 30: / Line 29: @@
 <!-- [[Category:SystemWideChange]] -->
-* Targeted release: [https://docs.fedoraproject.org/en-US/releases/f40/ Fedora Linux 40]
+* Targeted release: [https://docs.fedoraproject.org/en-US/releases/f41/ Fedora Linux 41]
 * Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
 <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
@@ Line 38: / Line 37: @@
 ON_QA -> change is fully code complete
 -->
-* [<will be assigned by the Wrangler> devel thread]
+* [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/VD2GVJPEM5MMJLSIJBER2IXV3IAVIM53/ Announced]
-* FESCo issue: <will be assigned by the Wrangler>
+* [https://discussion.fedoraproject.org/t/f40-change-proposal-haskell-ghc-9-6-and-stackage-lts-22-self-contained/99847 Discussion thread]
-* Tracker bug: <will be assigned by the Wrangler>
+* FESCo issue: [https://pagure.io/fesco/issue/3133 #3133]
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2258070 #2258070]
 * Release notes tracker: <will be assigned by the Wrangler>
 == Detailed Description ==
-For Fedora 40, the main [https://www.haskell.org/ghc/ GHC] Haskell compiler package will be updated from version [https://www.haskell.org/ghc/download_ghc_9_4_5.html 9.4.5] to the latest stable [https://www.haskell.org/ghc/download_ghc_9_6_3.html 9.6.3] release (rebasing the [https://src.fedoraproject.org/rpms/ghc9.6/ ghc ghc] package with the [https://src.fedoraproject.org/rpms/ghc9.6/ ghc9.6] package).
+For Fedora 40, the main [https://www.haskell.org/ghc/ GHC] Haskell compiler package will be updated from version [https://www.haskell.org/ghc/download_ghc_9_4_5.html 9.4.5] to the latest stable [https://www.haskell.org/ghc/download_ghc_9_6_4.html 9.6.4] or newer bugfix release (rebasing the [https://src.fedoraproject.org/rpms/ghc/ ghc] package with the [https://src.fedoraproject.org/rpms/ghc9.6/ ghc9.6] package).
 Along with this, Haskell packages in [https://www.stackage.org Stackage] (the stable Haskell source package distribution) will be updated from the versions in [https://www.stackage.org/lts-21 LTS 21] to latest [https://www.stackage.org/lts-22 LTS 22] release.
 Haskell packages not in Stackage will be updated to the latest appropriate version in the upstream [https://hackage.haskell.org Hackage] package repository.
@@ Line 52: / Line 52: @@
 == Benefit to Fedora ==
-<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
+Fedora users will have the latest stable Haskell compiler release, package tools, and current Haskell packages from latest Stackage LTS.
-      Be sure to include the following areas if relevant:
-      If this is a major capability update, what has changed?
-           For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
-      If this is a new functionality, what capabilities does it bring?
-           For example: This change allows package upgrades to be performed automatically and rolled-back at will.
-      Does this improve some specific package or set of packages?
-           For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
-      Does this improve specific Spins or Editions?
-           For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
-      Does this make the distribution more efficient?
-           For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
-      Is this an improvement to maintainer processes?
-           For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
-      Is this an improvement targeted as specific contributors?
-           For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.
-     When a Change has multiple benefits, it's better to list them all.
+GHC 9.6.4 is the latest current stable version of GHC with various enhancements and fixes (see the release notes linked in the Documentation section for more details about new features and improvements in 9.6).
-     Consider these Change pages from previous editions as inspiration:
-     https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
-     https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
-     https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
-     https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
-     https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
--->
 == Scope ==
 * Proposal owners:
-<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+** update rawhide ghc9.4 is build against itself
+** rebase ghc to 9.6.4
+** refresh packagings with the latest cabal-rpm release if needed
+** update packages to latest [https://www.stackage.org/lts-22 Stackage LTS 22] versions using cabal-rpm
+** build all the packages in a Koji sidetag repo in dependency order using fbrnch
+** push the sidetag through Bodhi to rawhide
+** deal with obsoleting ghc9.6 if needed
-* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Other developers: no actions should be needed <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 * Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 97: / Line 78: @@
 <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
-* Alignment with Community Initiatives:
+* Alignment with Community Initiatives: N/A
 <!-- Does your proposal align with the current Fedora Community Initiatives: https://docs.fedoraproject.org/en-US/project/initiatives/ ? It's okay if it doesn't, but it's something to consider -->
 == Upgrade/compatibility impact ==
-<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
+Any dropped packages will have obsoletes added.
+Otherwise there should not be any direct upgrade impact.
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+Users' Haskell projects will get built with ghc-9.6 when they next build them and might need some minor code tweaks
+(see the release notes linked below).
 == How To Test ==
-<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
+* install ghc and cabal-install
+* install pandoc, ShellCheck, ghcid, git-annex, hadolint, stack, xmonad, Agda
-Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
+* install ghc-*-devel or ghc-*-prof or ghc-*-doc
+* cabal-rpm builddep <favouritepackage>; cabal install <favouritepackage>
-A good "how to test" should answer these four questions:
+* install ghc8.10, ghc9.0, ghc9.2, ghc9.4, or ghc*devel
+* test upgrades of F39 Haskell packages to F40
-. What special hardware / data / etc. is needed (if any)?
-. How do I prepare my system to test this change? What packages
-need to be installed, config files edited, etc.?
-. What specific actions do I perform to check that the change is
-working like it's supposed to?
-. What are the expected results of those actions?
--->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 == User Experience ==
-<!-- If this change proposal is noticeable by users, how will their experiences change as a result?
+Users will have the most recent stable major version of `ghc` and Haskell libraries and tools available to them.
+This makes it easier to build the latest versions of Haskell projects.
- This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
- Describe what Users will see or notice, for example:
+In particular `cabal-install` will also be updated from 3.8 to 3.10, `pandoc` will be updated to 3.1, and `stack` to 2.13.
-  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
-  - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
- - Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
- - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
--->
 == Dependencies ==
@@ Line 145: / Line 111: @@
 <!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
-* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency mechanism:
-<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
+** Change owner will drop the new builds and revert dist-git back to the versions in F39
-* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency deadline: Beta Freeze
 <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
-* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 == Documentation ==
-<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+* https://downloads.haskell.org/~ghc/9.6.4/docs/html/users_guide/9.6.1-notes.html
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
 == Release Notes ==

Search

Changes/Haskell GHC 9.6 and Stackage 22: Difference between revisions