From Fedora Project Wiki
Line 106: Line 106:
== Contingency Plan ==
== Contingency Plan ==
<!-- 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.  -->
<!-- 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: revert ghc to current 7.6.3 and rebuild other packages if necessary (Proposal Owners) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency mechanism: if it is not possible to complete the building and testing in f22-build in time for the Mass Rebuild then ghc will be reverted back to current 7.6.3 and packages rebuilt as necessary. (Proposal Owners) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Contingency deadline: Beta Freeze  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency deadline: Beta Freeze  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release: No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks release: Yes <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product: N/A  <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
* Blocks product: N/A  <!-- Applicable for Changes that blocks specific product release/Fedora.next -->



Revision as of 07:24, 14 January 2015

GHC 7.8

Summary

Update the GHC Haskell compiler to the major new 7.8 release, and update/rebuild all Haskell packages against it.

Owner

Current status

Detailed Description

  • The involves updating ghc from 7.6.3 to 7.8.3 (or later), and updating/rebuilding all Fedora Haskell packages.
  • The initial work will be done locally offline to make sure that it is possible to build all our packages with ghc-7.8 and the latest updated libraries. [done]
  • A Koji side tag will then be used to build all the packages before the Side Tag Builds Deadline. [tag requested]
  • Once the packages have been tested, the builds will be moved into f22 in time for F22 Mass Rebuild.

Benefit to Fedora

GHC 7.8 is major new version of the major Haskell compiler with many new features and enhancements. See the upstream release notes link below for more details on the changes.

For example the new runtime I/O manager scales significantly better for larger workloads compared to the previous one: it should scale linearly up to approximately 32 cores (reference).

Scope

  • Proposal owners:
    • locally test rebuilding and updating of all packages
    • (optional) update macros to subpackage static libraries
    • push changes to Koji
    • testing
  • Other developers:
    • If you own a package which contains some Haskell code built with ghc you will need to rebuild you package to make sure it still rebuilds with ghc-7.8. Feel free to contact the Haskell SIG if we need assistance with fixing any build breakage, and we will try to help out.
  • Release engineering: not required
  • Policies and guidelines:
    • There may be some lesser changes to the Haskell Packaging Guidelines needed - they could be done after this Change.

Upgrade/compatibility impact

  • Upgrading will be tested and should Just Work.
  • Local user code may need some minor changes to build with ghc-7.8.

How To Test

  1. yum install ghc cabal-install cabal-rpm pandoc xmonad git-annex hledger
  2. Check these packages install, run correctly, and can build Haskell and Hackage packages.

User Experience

User using GHC to programming or develop in Haskell will benefit from the new features and performance enhancements of the latest version of the ghc compiler. Additionally various package upgrades will also improve the experience for users of Haskell packages.

Dependencies

  • GHC 7.8.3 was released 2014-07-11
  • GHC 7.8.4 bugfix released 2014-12-23

There are a few packages outside the Haskell SIG that use ghc for some part of their build. Assistance can be provided if needed to build them with latest ghc.

Contingency Plan

  • Contingency mechanism: if it is not possible to complete the building and testing in f22-build in time for the Mass Rebuild then ghc will be reverted back to current 7.6.3 and packages rebuilt as necessary. (Proposal Owners)
  • Contingency deadline: Beta Freeze
  • Blocks release: Yes
  • Blocks product: N/A

Documentation

http://www.haskell.org/ghc/docs/7.8.2/html/users_guide/release-7-8-1.html


Release Notes