@@ -26,7 +26,20 @@ After doing that commit with a message like "add foo-bar" and send a pull reques
2626The continuous integration job will do some checks to see if your package's dependencies are up-to-date.
2727
2828The CI job notably doesn't compile packages, run tests, build documentation, or find missing C libraries.
29−If you want to be proactive or if CI fails, you can make sure that your package builds against the newest versions of all dependencies like this:
29+If you want to be proactive or if CI fails, you can make sure that your package builds against the latest nightly:
30+
31+```
32+$ stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
33+```
34+
35+Or, if some dependencies haven't made it into Stackage Nightly yet:
36+
37+```
38+$ rm -f stack.yaml && stack init --resolver nightly --solver
39+```
40+
41+Or, alternatively, with `cabal` (may end up using older dependency
42+versions):
3043
3144```
3245$ ghc --version # Should be the same as the latest nightly, it's in the title of https://www.stackage.org/nightly
@@ -139,6 +152,13 @@ If your package ends up being temporarily disabled from Stackage
139152Nightly, please simply send a pull request to add it back once it and
140153its dependencies are compatible with the newest GHC version.
141154
155+Note that it is _not_ a goal of LTS Haskell to track the latest
156+version of GHC. If you want the latest and greatest, Stackage Nightly
157+is your best bet. In particular, LTS Haskell will often—but not
158+always—avoid upgrading to the first point release of GHC
159+releases (e.g., 8.2.1) to allow further testing and to get the
160+benefits of the first bugfix release (e.g., 8.2.2).
161+
142162## Adding a package to an LTS snapshot
143163
144164The steps above affect the Stackage Nightly builds, but do not directly affect