@@ -291,7 +291,10 @@ we're just not there yet.
292Recommended: run these from inside a `tmux` session. If you get version bound
292Recommended: run these from inside a `tmux` session. If you get version bound
293problems on nightly or LTS major, you need to fix build-constraints.yaml (see
293problems on nightly or LTS major, you need to fix build-constraints.yaml (see
296+### Building LTS minor releases
294−info above). For an LTS minor bump, you'll typically want to:
297+For an LTS minor bump, you'll typically want to:
296* Add constraints to package `range:` fields in eg `work/lts14/constraints.yaml`.
299* Add constraints to package `range:` fields in eg `work/lts14/constraints.yaml`.
297* Add new packages versioned to eg `work/lts14/snapshot-incomplete.yaml` (the `@<hash>` suffix is optional)
300* Add new packages versioned to eg `work/lts14/snapshot-incomplete.yaml` (the `@<hash>` suffix is optional)
@@ -313,7 +316,7 @@ if one needs to revert one package, say due to a build or test regression,
313one can edit `current-plan.yaml` and updated the SHA256 hash of the .cabal file,
316one can edit `current-plan.yaml` and updated the SHA256 hash of the .cabal file,
314to avoid having to rebuild everything again.)
317to avoid having to rebuild everything again.)
316−_Sadly no longer true currently_: ~~Note LTS builds inherit the current Hackage data (stack updated for Nigthly) to avoid excess extra rebuilding.~~
319+_Sadly no longer true currently_: ~~Note LTS builds inherit the current Hackage data (stack updated for Nightly) to avoid excess extra rebuilding.~~
318### Timing
321### Timing