<div dir="ltr"><div>Hi Ben,</div><div><br></div><div>Since part of the changes of <a href="https://gitlab.haskell.org/ghc/ghc/-/issues/14422">https://gitlab.haskell.org/ghc/ghc/-/issues/14422</a> are already merged into master (e.g. we ignore the "type signature" part of a COMPLETE sig now, because there is nothing to disambiguate), it would be good if we merged the solution outlined in <a href="https://gitlab.haskell.org/ghc/ghc/-/issues/14422#note_321645">https://gitlab.haskell.org/ghc/ghc/-/issues/14422#note_321645</a>, as that would allow users to switch to a new, better mechanism instead of discovering that COMPLETE signatures seemingly have been ripped of a feature.<br>The problem with that is that it needs a GHC proposal, I think, and that's not written yet.</div><div><br></div><div>Also I hope to merge some efforts in the CPR area before the fork. But that's quite optional.</div><div><br></div><div>Cheers,</div><div>Sebastian<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am Do., 4. Feb. 2021 um 19:56 Uhr schrieb Ben Gamari <<a href="mailto:ben@well-typed.com">ben@well-typed.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
tl;dr. Provisional release schedule for 9.2 enclosed. Please discuss,<br>
especially if you have something you would like merged for 9.2.1.<br>
<br>
Hello all,<br>
<br>
With GHC 9.0.1 at long-last out the door, it is time that we start<br>
turning attention to GHC 9.2. I would like to avoid making the mistake<br>
made in the 9.0 series in starting the fork in a state that required a<br>
significant amount of backporting to be releaseable. Consequently, I<br>
want to make sure that we have a fork schedule that is realistic given<br>
the things that need to be merged for 9.2. These include:<br>
<br>
* Update haddock submodule in `master` (Ben)<br>
* Bumping bytestring to 0.11 (#19091, Ben)<br>
* Finishing the rework of sized integer primops (#19026, John Ericson)<br>
* Merge of ghc-exactprint into GHC? (Alan Zimmerman, Henry)<br>
* Merge BoxedRep (#17526, Ben)<br>
* ARM NCG backend and further stabilize Apple ARM support? (Moritz)<br>
* Some form of coercion zapping (Ben, Simon, Richard)<br>
* Tag inference analysis and tag check elision (Andreas)<br>
<br>
If you see something that you would like to see in 9.2.1 please do<br>
holler. Otherwise, if you see your name in this list it would be great<br>
if you could let me know when you think your project may be in a<br>
mergeable state.<br>
<br>
Ideally we would strive for a schedule like the following:<br>
<br>
4 February 2021: We are here<br>
~4 weeks pass<br>
3 March 2021: Release branch forked<br>
1 week passes<br>
10 March 2021: Alpha 1 released<br>
3 weeks pass <br>
31 March 2021: Alpha 2 released<br>
2 weeks pass<br>
14 April 2021: Alpha 3 released<br>
2 weeks pass<br>
28 April 2021: Alpha 4 released<br>
1 week passes<br>
5 May 2021: Beta 1 released<br>
1 week passes<br>
12 May 2021: Release candidate 1 released<br>
2 weeks pass<br>
26 May 2021: Final release<br>
<br>
This provides ample time for stabilization while avoiding deviation from<br>
the usual May release timeframe. However, this would require that we<br>
move aggressively to start getting the tree into shape since the fork<br>
would be less than four weeks away. I would appreciate contributors'<br>
thoughts on the viability of this timeline.<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>