git.iko.soy/stackage
on master help sign in
CURATORS: emphasize that range must be put under source

Otherwise constraints are just ignore and will be breakage will reappear on the next build-next.sh without NOPLAN

commite9b227bbf8cd7a208db373a48ba4a43fb81cdb68 authorJens Petersen <juhpetersen@gmail.com> dateTue 28 Jan 2020, 11:03 (7 years ago) parentdb3f6b7
1 file changed+1−1
compare with master
unifiedsplit
CURATORS.md+1−1
CURATORS.md+1−1
@@ -298,7 +298,7 @@ First run `build-next.sh` to regenerate updated `ltsXX/work/constraints.yaml` an
298298
299299For an LTS minor bump, you'll typically want to:
300300
301−* Add constraints to package `range:` fields in that `constraints.yaml`.
301+* Add constraints to package `range:` fields _under_ the `source:` field in that `constraints.yaml`.
302302* Add new packages versioned to `snapshot-incomplete.yaml` (the `@<hash>` suffix is optional)
303303* Test, benchmark, haddock failures can also be added to package fields in the `constraints.yaml` if necessary, though it should be avoided if possible for LTS.
304304