FAQ: refresh "why LTS ghc old?"

lts17 was released with 8.10.3
This commit is contained in:
Jens Petersen 2021-01-26 15:06:32 +08:00 committed by GitHub
parent f21bdc26e7
commit 9969cca46d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -92,13 +92,12 @@ __Why is Stackage LTS still on an older version of GHC?__
Typically it takes some months from a new major ghc release before Typically it takes some months from a new major ghc release before
the Haskell ecosystem supports it fully enough that we can push it the Haskell ecosystem supports it fully enough that we can push it
to a new stable Stackage major version release. The lag for minor ghc releases to a new stable Stackage major version release. There can also be
should be less but it still requires extra work and there is usually ghc regressions that hold up a LTS major release.
some delay, but this also allows for sufficient community testing before updating.
eg Currently there is a 8.10.2 issue with linking on Windows. The lag for minor ghc releases should be less
Once 8.10.3 is out and we are satisfied it is working well in Nightly but it still requires extra work and there is usually some delay - this also
we will plan to move to release LTS 17 based on ghc-8.10. allows for some community testing before updating LTS.
__Why does Stackage have an older version of a package than Hackage?__ __Why does Stackage have an older version of a package than Hackage?__