<div dir="ltr">Hi all.<div><br></div><div>I'd like to get !1730 in, and ideally !1739 if it doesn't require a proposal.</div><div><br></div><div>Sandy</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Sep 22, 2019 at 4:23 AM Artem Pelenitsyn <<a href="mailto:a.pelenitsyn@gmail.com">a.pelenitsyn@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hello Ben,</div><div><br></div><div>I hope to push the threaded RTS by default MR over the line now when the GHC proposal has been accepted.</div><div><br></div><div>Here is the MR: <a href="https://gitlab.haskell.org/ghc/ghc/merge_requests/538" target="_blank">https://gitlab.haskell.org/ghc/ghc/merge_requests/538</a></div><div><br></div><div>It has some unstable test suite failures: they appear only in some configurations. <br></div><div>Notably, validate-x86_64-linux-deb9-debug fails more than others:<br></div><div><a href="https://gitlab.haskell.org/ulysses4ever/ghc/pipelines/10289" target="_blank">https://gitlab.haskell.org/ulysses4ever/ghc/pipelines/10289</a></div><div>I'd appreciate if someone could take a look and suggest a path forward.</div><div><br></div><div>--</div><div>Best wishes,</div><div>Artem<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 18 Sep 2019 at 16:08, Ben Gamari <<a href="mailto:ben@well-typed.com" target="_blank">ben@well-typed.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">tl;dr. If you have unmerged work that you would like to be in GHC 8.10 please<br>
reply to this email and submit it for review in the next couple<br>
of weeks.<br>
<br>
<br>
Hello everyone,<br>
<br>
Now that GHC 8.8.1 is behind us it is time that we begin thinking about<br>
8.10. There seems to be broad consensus within the subset of the<br>
community that I sampled that we should try to hold to the usual release<br>
date near the end of year for 8.10.1. I believe that this is a feasible<br>
goal with the caveat that we push the final release back by a couple of<br>
weeks in recognition that busy schedules of the holiday season tends to<br>
throw unexpected wrenches into the release process.<br>
<br>
In particular I would suggest the following concrete schedule:<br>
<br>
October 18 2019: start of one week freeze in preparation for branching<br>
October 25 2019: ghc-8.10 branch cut<br>
November 8 2019: 8.10.1-alpha1<br>
November 22 2019: 8.10.1-alpha2<br>
December 6 2019: 8.10.1-alpha3<br>
December 20 2019: 8.10.1-rc1<br>
January 10 2020: Final 8.10.1 release<br>
<br>
If you have yet-unmerged work that you would like to see in GHC 8.10<br>
please do be in touch and open a merge request ASAP.<br>
<br>
<br>
One obvious question is how we will avoid the many delays that plagued<br>
the 8.8.1 release. Without delving too deep into the specific reasons for<br>
these delays, the reasons fell into two buckets:<br>
<br>
1. delays due to CI stabilization<br>
2. coordination delays with upstream libraries<br>
3. fallout from MonadFail changes which landed only late in the release<br>
cycle<br>
<br>
Of these, (1) is largely behind us and (3) will be avoided by ensuring<br>
that core libraries changes are landed *before* the branch date.<br>
<br>
This leaves consideration (2). The problem of upstream library<br>
coordination has always been a tricky one but has grown more acute as<br>
our release schedule has accelerated. While no technical solution will<br>
eliminate the issue entirely, we believe that decoupling GHC's release<br>
schedule from those of its dependencies' is an important mitigation.<br>
We will be discussing this with upstream library maintainers in<br>
the coming weeks to establish how we can ensure that releases are<br>
available well ahead of the GHC 8.10 release, ideally by alpha2.<br>
<br>
Cheers,<br>
<br>
- Ben<br>
_______________________________________________<br>
ghc-devs mailing list<br>
<a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
</blockquote></div>
_______________________________________________<br>
ghc-devs mailing list<br>
<a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>I'm currently travelling the world, sleeping on people's couches and doing full-time collaboration on Haskell projects. If this seems interesting to you, please consider signing up as a host! <a href="https://isovector.github.io/erdos/" target="_blank">https://isovector.github.io/erdos/</a><br></div></div></div></div></div>