A modest proposal (re the Platform)
Carter Schonwald
carter.schonwald at gmail.com
Fri Jan 24 05:25:30 UTC 2014
Jens,
are you willing to undertake providing support for all the problems in
current 7.6 on ALL platforms right now?
Are you willing to test the builds on all platforms, and be the person to
help everyone who's hitting issues?
doing an HP release now will push back the release timeline of an HP
version with 7.8 that has full first class support for 10.9 clang quirks +
the win64 fixes that are landing in head this past week, along with a whole
slew of other ecosystem amazing improvements.
I suspect the next HP will be using 7.8.2, because certain final steps of
the windows fixes are slated for that release, though maybe things'll move
up and get fixed in 7.8.1. I could be wrong mind you.
I'm *quite super duper happy* that the next HP will be 7.8.
On Thu, Jan 23, 2014 at 11:04 PM, Jens Petersen
<juhp at community.haskell.org>wrote:
> I know it is difficult but if ghc and haskell-platform could align
>> their schedules better then things might be easier to plan in the future.
>>
>
> Really I would like to see a HP release now *and* one after 7.8.1! :)
> I think HP beta releases should follow each ghc release
> and there can be additional point release updates as needed
> between major ghc releases. The stable HP release would come
> from the latest stable ghc release. So ideally we could have an
> updated stable release based on 7.6.3 and an alpha/beta release
> after 7.8.1 is released. For such pre-releases the binaries do not
> have to be ready on the release day just a source tarball.
> RCs with binaries once tested could be promoted to stable releases.
>
> _______________________________________________
> Haskell-platform mailing list
> Haskell-platform at projects.haskell.org
> http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20140124/299377a0/attachment-0001.html>
More information about the ghc-devs
mailing list