@@ -283,28 +283,21 @@ we're just not there yet.
283/opt/stackage-build/stackage/automated/run-nightly.sh
283/opt/stackage-build/stackage/automated/run-nightly.sh
285# Run an LTS minor bump
285# Run an LTS minor bump
286−/opt/stackage-build/stackage/automated/build.sh lts-2.17
286+/opt/stackage-build/stackage/automated/build-next.sh lts-14.17
288# Run an LTS major bump
288# Run an LTS major bump
289−/opt/stackage-build/stackage/automated/build.sh lts-3.0
289+/opt/stackage-build/stackage/automated/build-next.sh lts-15.0
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
294−info above). For an LTS minor bump, you'll typically want to use the
294+info above). For an LTS minor bump, you'll typically want to:
295−`CONSTRAINTS` environment variable, e.g.:
297−```
296+* Add constraints to package `range:` fields in eg `work/lts14/constraints.yaml`.
298−CONSTRAINTS='--constraint "conduit < 1.4.5" --constraint "criterion < 1.2.3"' /opt/stackage-build/stackage/automated/build.sh lts-2.17
297+* Add new packages versioned to eg `work/lts14/snapshot-incomplete.yaml` (the `@<hash>` suffix is optional)
299−```
298+* Test, benchmark, haddock failures can also be added to package fields in eg `work/lts14/constraints.yaml` if necessary, though it should be avoided if possible for LTS.
301−Valid arguments to include in this environment variable:
303−* `--constraint` to modify an upper or lower bound
300+This replaces `CONSTRAINTS=...' /opt/stackage-build/stackage/automated/build.sh lts-x.y` for the old curator-1.
304−* `--add-package` to add a brand new package
305−* `--expect-test-failure` to expect tests to fail
306−* `--expect-haddock-failure` to expect haddocks to fail
307−* `--expect-bench-failure` to expect benchmarks to fail
309If a build fails for bounds reasons, see all of the advice above. If the code
302If a build fails for bounds reasons, see all of the advice above. If the code
310itself doesn't build, or tests fail, open up an issue and then either put in a
303itself doesn't build, or tests fail, open up an issue and then either put in a
@@ -320,7 +313,7 @@ if one needs to revert one package, say due to a build or test regression,
320one can edit `current-plan.yaml` and updated the SHA256 hash of the .cabal file,
313one can edit `current-plan.yaml` and updated the SHA256 hash of the .cabal file,
321to avoid having to rebuild everything again.)
314to avoid having to rebuild everything again.)
323−Note LTS builds inherit the current Hackage data (stack updated for Nigthly) to avoid excess extra rebuilding.
316+_Sadly no longer true currently_: ~~Note LTS builds inherit the current Hackage data (stack updated for Nigthly) to avoid excess extra rebuilding.~~
325### Timing
318### Timing