From Fedora Project Wiki
< Changes
(Created page with "= GHC 7.8 = == Summary == Update the ghc Haskell compiler to new 7.8 release, and update/rebuild all Haskell packages against it. == Owner == * Name: [[User:Petersen| Jens P...") |
(make system wide) |
||
| Line 2: | Line 2: | ||
== Summary == | == Summary == | ||
Update the | Update the GHC Haskell compiler to the major new 7.8 release, and update/rebuild all Haskell packages against it. | ||
== Owner == | == Owner == | ||
* Name: [[User:Petersen| Jens Petersen]] | * Name: [[User:Petersen| Jens Petersen]], [[USer:codeblock|Ricky Elrod]], [[Haskell_SIG]] | ||
* Email: petersen@redhat.com | * Email: petersen@redhat.com, relrod@redhat.com, haskell@lists.fedoraproject.org | ||
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
| Line 18: | Line 18: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/21 | Fedora 21 ]] | * Targeted release: [[Releases/21 | Fedora 21 ]] | ||
* Last updated: 2014- | * Last updated: 2014-04-01 | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
Bugzilla states meaning as usual: | Bugzilla states meaning as usual: | ||
| Line 38: | Line 38: | ||
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 ([http://www.reddit.com/r/haskell/comments/18d81l/ghc_head_new_parallel_io_manager_merged/ reference]). | 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 ([http://www.reddit.com/r/haskell/comments/18d81l/ghc_head_new_parallel_io_manager_merged/ reference]). | ||
See the release notes link for more details. | See the release notes link below for more details. | ||
== Scope == | == Scope == | ||
| Line 49: | Line 49: | ||
** testing | ** testing | ||
* Other developers: | * 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. <!-- 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?--> | <!-- 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: | * Release engineering: not required <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | ||
* Policies and guidelines: | * Policies and guidelines: there may be some lesser changes to the Haskell Packaging Guidelines - they could be done after this Change.<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | ||
| Line 62: | Line 62: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Upgrading will be tested and should Just Work. | |||
== How To Test == | == How To Test == | ||
| Line 78: | Line 78: | ||
3. What are the expected results of those actions? | 3. What are the expected results of those actions? | ||
--> | --> | ||
1. yum install ghc cabal-install cabal-rpm pandoc xmonad git-annex hledger | |||
2. Check these packages install, run correctly, and can build Haskell packages. | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 85: | Line 88: | ||
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
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 == | == Dependencies == | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | ||
GHC 7.8.1 should be released very soon. | |||
There are a few packages outside the Haskell SIG that use ghc for some part of their build. | There are a few packages outside the Haskell SIG that use ghc for some part of their build. | ||
| Line 98: | Line 104: | ||
== 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: | * Contingency mechanism: Owners will revert ghc to current 7.6.3 and rebuild other packages if necessary <!-- 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: | * 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 | * Blocks release: No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* Blocks product | * Blocks product: N/A <-- Applicable for Changes that blocks specific product release/Fedora.next --> | ||
== Documentation == | == Documentation == | ||
| Line 126: | Line 132: | ||
<!-- Select proper category, default is Self Contained Change --> | <!-- Select proper category, default is Self Contained Change --> | ||
[[Category:SelfContainedChange]] | <!-- [[Category:SelfContainedChange]] --> | ||
[[Category:SystemWideChange]] | |||
Revision as of 09:00, 1 April 2014
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
- Name: Jens Petersen, Ricky Elrod, Haskell_SIG
- Email: petersen@redhat.com, relrod@redhat.com, haskell@lists.fedoraproject.org
- Release notes owner:
Current status
- Targeted release: Fedora 21
- Last updated: 2014-04-01
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
The involves updating ghc from 7.6.3 to 7.8.1 (or later), and rebuilding/updating all Fedora Haskell packages. The initial work will be done offline locally to make sure that it is possible to build all our packages with ghc-7.8 and latest libraries. Once that is completed, building will be done into Koji for rawhide and testing done.
Benefit to Fedora
GHC 7.8 is major new version of the major Haskell compiler with many new features and enhancements.
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). See the release notes link below for more details.
Scope
- Proposal owners:
- locally test rebuilding and updating of all packages
- 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 - they could be done after this Change.
Upgrade/compatibility impact
Upgrading will be tested and should Just Work.
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 packages.
N/A (not a System Wide Change)
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.1 should be released very soon.
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: Owners will revert ghc to current 7.6.3 and rebuild other packages if necessary
- Contingency deadline: Beta Freeze
- Blocks release: No
- Blocks product: N/A <-- Applicable for Changes that blocks specific product release/Fedora.next -->
Documentation
http://www.haskell.org/ghc/docs/7.8.1-rc2/html/users_guide/release-7-8-1.html