@@ -94,7 +94,19 @@ You can try this when you notice that a package has been updated. You
9494can also periodically try to lift bounds (I think it's good to do this
9595at the start of your week /@bergmark)
9696
97−If stackage-curator is happy commit the change ("Remove upper bounds and close #X").
97+If not all packages have been updated check if any of them are missing
98+from the original issue and if so add a new comment mentioning them. A
99+new package may appear if its dependencies were part of this issue but
100+have been updated since the last time we checked. We want to give
101+these new packages ample time to be upgraded.
102+
103+If stackage-curator is happy commit the change ("Remove upper bounds
104+and close #X"). After doing this the next nightly build may fail
105+because some packages didn't have an upper bound in place, but
106+compilation failed. In this case revert the previous commit so any
107+disabled packages are enabled again, re-open the issue, and add a new
108+comment with the failing packages. This is to give all maintainers
109+enough time to upgrade for this case as well.
98110
99111### Amending upper bounds
100112
@@ -154,9 +166,12 @@ Comment out the offending packages from the "packages" section and add
154166a comment saying why it was disabled:
155167
156168```
157− # - swagger # BLOCKED aeson 1.0
169+ # - swagger # bounds: aeson 1.0
158170```
159171
172+If this causes reverse dependencies to be disabled we should notify
173+the maintainers of those packages.
174+
160175
161176## Updating the content of the Docker image used for building
162177