This is a tracking bug for Change: GHC 7.8 For more details, see: http://fedoraproject.org//wiki/Changes/GHC_7.8 Update the GHC Haskell compiler to the major new 7.8 release, and update/rebuild all Haskell packages against it.
Just for the record a preliminary build for testing is available from https://copr.fedoraproject.org/coprs/petersen/ghc-7.8
It seems also there will be a 7.8.2 release soon due a bug found in 7.8.1. It is not clear yet when Haskell Platform for 7.8 will be released but it doesn't really need to block us.
This message is a reminder that Fedora 21 Accepted Changes Freeze Deadline is on 2014-07-08 [1]. At this point, all accepted Changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be so enabled at Change Freeze. This bug should be set to the MODIFIED state to indicate that it achieved completeness. Status will be provided to FESCo right after the deadline. If, for any reasons, your Change is not in required state, let me know and we will try to find solution. For Changes you decide to cancel/move to the next release, please use the NEW status and set needinfo on me and it will be acted upon. In case of any questions, don't hesitate to ask Wrangler (jreznik). Thank you. [1] https://fedoraproject.org/wiki/Releases/21/Schedule
ghc-7.8.2 was released in April but it is somewhat buggy. ghc-7.8.3 release was expected early June but it is still slipping but I think it will come out soon. Of course problem is after branching it will be quite a bit more work to backport ghc-7.8 to F21, but I think it should possible to finish that well before the Beta freeze. I also plan to do a copr SCL for ghc783 for earlier releases.
Just to update that upstream has released the src tarball for 7.8.3 now to developers, though the release has not been officially announced yet.
ghc-7.8.3 was officially released 11th July.
(In reply to Jens Petersen from comment #6) > ghc-7.8.3 was officially released 11th July. Do you have any ETA on packaging?
Sorry for long silence: well work is still in progress for Rawhide currently which is the initial target. I assume we missed the boat for F21?
This message is a reminder that Fedora 21 Change Checkpoint: 100% Code Complete Deadline (Former Accepted Changes 100% Complete) is on 2014-10-14 [1]. All Accepted Changes has to be code complete and ready to be validated in the Beta release (optionally by Fedora QA). Required bug state at this point is ON_QA. As for several System Wide Changes, Beta Change Deadline is a point of contingency plan. All incompleted Changes will be reported to FESCo on 2014-10-15 meeting. In case of any questions, don't hesitate to ask Wrangler (jreznik). [1] https://fedoraproject.org/wiki/Releases/21/Schedule
(In reply to Jens Petersen from comment #8) > Sorry for long silence: well work is still in progress for Rawhide > currently which is the initial target. I assume we missed the > boat for F21? Jens, how far are you? Boat is departing right now. I see 7.6.3 in Koji, so I expect you missed it, right? if so, I'll do all required changes to postpone it to Fedora 22.
Yes, given that it is not in Rawhide I think we will postpone this to F22, for which it should be ready in good time. (Most of it can build now but we are still missing some new deps for some leave packages.)
Ok, thanks Jens!
We won't need a release note for F21 then; setting the flag to -.
286 packages have been built for f22. There are still a lose ends to tidy up but this work is largely finished now.
This message is a reminder that Fedora 22 Change Checkpoint: Completion deadline (testable) is on 2015-02-24 [1]. At this point, all accepted Changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be so enabled at Change Completion deadline. This bug should be set at least to the MODIFIED state to indicate that it achieved completeness. Status will be provided to FESCo right after the deadline. If, for any reasons, your Change is not in required state, let me know and we will try to find solution. Fedora 22 is going to be strictly time based release. For Changes you decide to cancel/move to the next release, please use the NEW status and set needinfo on me and it will be acted upon. In case of any questions, don't hesitate to ask Wrangler (jreznik). Thank you. [1] https://fedoraproject.org/wiki/Releases/22/Schedule
This message is a reminder that Fedora 22 "Change Checkpoint: 100% Code Complete Deadline" is on 2015-03-31 [1]. All Accepted Changes has to be code complete and ready to be validated in the Beta release (optionally by Fedora QA). Required bug state at this point is ON_QA. As for several System Wide Changes, Beta Freeze is a point of contingency plan, all incomplete Changes will be reported to FESCo for 2015-04-01 meeting. In case of any questions, don't hesitate to ask Wrangler (jreznik). [1] https://fedoraproject.org/wiki/Releases/22/Schedule
Jens, is GHC 7.8 change considered to be completed? See above. If yes, please mark it as ON_QA. Thanks.
There are still a few loose ends like Agda and aarch64, but I think it is basically 99% done.
(In reply to Jens Petersen from comment #18) > There are still a few loose ends like Agda and aarch64, > but I think it is basically 99% done. ghc is built now for aarch64, and Agda building now for f23: once done I will build it also for f22.
Hello Jens, we'd like to include this change in the Fedora 22 Beta Release Notes. Please take a look at the draft I posted into the Doc Text field, and let me know if this text is sufficient, or if there's anything you'd like to add or change. Thanks!
Petr, your text looks to me! Thanks