From Fedora Project Wiki
 
(6 intermediate revisions by one other user not shown)
Line 7: Line 7:
* Name: [[User:Petersen| Jens Petersen]], [[Haskell_SIG]]
* Name: [[User:Petersen| Jens Petersen]], [[Haskell_SIG]]
* Email: <petersen@redhat.com>, <haskell@lists.fedoraproject.org>
* Email: <petersen@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> --> [mailto:sclark@fedoraproject.org Simon Clark] ([[User:sclark|sclark]])
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
Line 44: Line 44:
** We will follow versions from latest Stackage LTS 8.2
** We will follow versions from latest Stackage LTS 8.2


* Other developers: Negligible work outside Haskell SIG, but the SIG can try to help resolve any issues which should arise. [hedgewars pending]
* Other developers: Negligible work outside Haskell SIG, but the SIG can try to help resolve any issues which should arise. [done]
<!-- 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: f26-ghc needs to be created and once all rebuilding there is completed the builds need to be tagged into f26 ([https://pagure.io/releng/issue/6639 ticket])
* Release engineering: f26-ghc needs to be created and once all rebuilding there is completed the builds need to be tagged into f26 [done]
<!-- 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.  
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.-->
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.-->
Line 78: Line 78:
-->
-->


* `dnf install ghc cabal-install pandoc`
* <code>dnf install ghc cabal-install alex happy pandoc hlint</code>
* `dnf install ghc-*-devel`
* <code>dnf install @haskell</code>
* <code>dnf install ghc-*-devel</code>


== User Experience ==
== User Experience ==
Line 98: Line 99:
<!-- 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: (What to do?  Who will do it?)
* Contingency mechanism: (What to do?  Who will do it?)
** If any key packages or sufficient number can't be updated and built in time, we (owner) will drop the all partial builds in f26-ghc and revert git master branches to the current ghc-7.10 package set from F25.
** If any key packages or sufficient number can't be updated and built in time, we (owner) will drop all the partial builds in f26-ghc and revert git master branches to the current ghc-7.10 package set from F25.
<!-- 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: before Mass Rebuild
* Contingency deadline: before Mass Rebuild
Line 116: Line 117:
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
-->
-->
The GHC Haskell Compiler has been upgraded to version 8.0.2, and all Haskell rebuilt and many updated.
The GHC Haskell Compiler has been upgraded to version 8.0.2, and all Haskell packages rebuilt and many updated.


[[Category:ChangeAcceptedF26]]
[[Category:ChangeAcceptedF26]]

Latest revision as of 21:01, 3 July 2017

GHC 8.0

Summary

Update the GHC Haskell compiler in Fedora from version 7.10 to the current stable version 8.0, with much improved support for aarch64, ppc64, and ppc64le.

Owner

Current status

Detailed Description

GHC 8.0 contains many new features, fixes, and improvements including performance. Other distros are already moving to it and Fedora users will benefit from it too. This will require updating some and rebuilding all of the Haskell packages in Fedora.

Benefit to Fedora

Fedora users will be able to use the latest stable version of the GHC Haskell compiler, and enjoy new features, bugfixes, and performance improvements.


Scope

  • Proposal owners: all building work will be done in f26-ghc [done]
    • We will follow versions from latest Stackage LTS 8.2
  • Other developers: Negligible work outside Haskell SIG, but the SIG can try to help resolve any issues which should arise. [done]
  • Release engineering: f26-ghc needs to be created and once all rebuilding there is completed the builds need to be tagged into f26 [done]
  • Policies and guidelines: no Haskell Packaging changes currently planned
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

System upgrades should be smooth but users may have to update their code to make it recompile after upgrading.

How To Test

  • dnf install ghc cabal-install alex happy pandoc hlint
  • dnf install @haskell
  • dnf install ghc-*-devel

User Experience

They will have access to GHC 8.0 in Fedora, and be able to install and use it easily.


Dependencies

Very few packages with any Haskell dependencies outside the Haskell SIG.

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?)
    • If any key packages or sufficient number can't be updated and built in time, we (owner) will drop all the partial builds in f26-ghc and revert git master branches to the current ghc-7.10 package set from F25.
  • Contingency deadline: before Mass Rebuild
  • Blocks release? No

Documentation

Release Notes

The GHC Haskell Compiler has been upgraded to version 8.0.2, and all Haskell packages rebuilt and many updated.