From e9b227bbf8cd7a208db373a48ba4a43fb81cdb68 Mon Sep 17 00:00:00 2001
From: Jens Petersen <juhpetersen@gmail.com>
Date: Tue, 28 Jan 2020 11:03:26 +0800
Subject: [PATCH] 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
---
 CURATORS.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CURATORS.md b/CURATORS.md
index 0f4492a4..6b06c61c 100644
--- a/CURATORS.md
+++ b/CURATORS.md
@@ -298,7 +298,7 @@ First run `build-next.sh` to regenerate updated `ltsXX/work/constraints.yaml` an
 
 For an LTS minor bump, you'll typically want to:
 
-* Add constraints to package `range:` fields in that `constraints.yaml`.
+* Add constraints to package `range:` fields _under_ the `source:` field in that `constraints.yaml`.
 * Add new packages versioned to `snapshot-incomplete.yaml` (the `@<hash>` suffix is optional)
 * 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.