<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">The underlying issue is that, with finite resources, it is hard to support multiple releases long term. We can't really support 9.6, 9.8, 9.10, and HEAD. So the blog post was trying to be transparent, by saying that we'll focus efforts on 9.6, 9.10, and HEAD.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Is 9.6 the right choice? We think so but, as Ben asys, it would be great to have some more objective basis on which to assess uptake. In particular, it'd be great to have some telemetry. Telemetry is a complex issue -- but we now have some very well-informed colleagues: the team at Scarf. So maybe we'll get some basic data before long, which would be a big step forward. (We'd expect to be transparent about that too of course!)</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Simon<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 28 May 2024 at 17:37, Ben Gamari <<a href="mailto:ben@smart-cactus.org">ben@smart-cactus.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Clinton Mead <<a href="mailto:clintonmead@gmail.com" target="_blank">clintonmead@gmail.com</a>> writes:<br>
<br>
> Hi All<br>
><br>
> The recent GHC blog post:<br>
> <a href="https://www.haskell.org/ghc/blog/20240521-ghc-release-priorities.html" rel="noreferrer" target="_blank">https://www.haskell.org/ghc/blog/20240521-ghc-release-priorities.html</a><br>
> states:<br>
><br>
> *"9.6.5 seems to be a relatively stable release so far and we plan to<br>
> prioritise fixes given the relatively higher adoption of this branch"*<br>
><br>
> I was wondering where this information came from? Is this based on a number<br>
> of downloads or some other metric? Number of companies that have adopted<br>
> the version? How many stack/ghcup pulls? Or just a vibe/what people seem to<br>
> be talking about?<br>
><br>
> If there are hard numbers, are they public?<br>
><br>
Sadly we don't have hard numbers. However, we do try to keep an eye on a<br>
few "softer" metrics:<br>
<br>
* which releases tend to see the most new tickets<br>
* which releases tend to come up in online discussion<br>
* how much of the ecosystem has adapted to which releases<br>
<br>
I will admit that I'm not entirely happy with the amount of judgement<br>
that goes into determining support windows currently. My tick-tock<br>
release cadence proposal [1] was an attempt at proposing a more<br>
predictable schedule, but sadly it never gained much support.<br>
<br>
> The current project I'm working on is still on GHC 9.2.2, so I was<br>
> considering an upgrade to GHC 9.4.8, but this blog post has made me lean<br>
> towards the 9.6 series instead. This is just an upgrade for stability not<br>
> features and so we don't get too far behind. But it would be good to have<br>
> this popularity info generally instead of having to wait for a blog post.<br>
><br>
9.4 likely isn't the best upgrade target at this point. We will likely<br>
[status] not produce any further releases in this series and our attention<br>
has turned primarily to 9.10 and 9.6.<br>
<br>
[status]: <a href="https://gitlab.haskell.org/ghc/ghc/-/wikis/GHC-status" rel="noreferrer" target="_blank">https://gitlab.haskell.org/ghc/ghc/-/wikis/GHC-status</a><br>
[tick-tock]: <a href="https://github.com/haskellfoundation/tech-proposals/pull/34" rel="noreferrer" target="_blank">https://github.com/haskellfoundation/tech-proposals/pull/34</a><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>