doc/submitting-changes: should -> must
To me, as a native English speaker, this doesn't change the meaning of
the sentence at all. But to a non-native speaker, this can read like
the staging-next rules are only recommendations. Let's make this
clearer.
commitdc3dea22be2efd25517be358bb6bce64c670d318
authorAlyssa Ross <hi@alyssa.is>
dateSun 23 May 2021, 15:31 (5 years ago)
parente438e6e
doc/contributing/submitting-changes.chapter.md+1−1
@@ -238,7 +238,7 @@ The `staging` branch is a development branch where mass-rebuilds go. It should o
238238
239239### Staging-next branch {#submitting-changes-staging-next-branch}
240240
241−The `staging-next` branch is for stabilizing mass-rebuilds submitted to the `staging` branch prior to merging them into `master`. Mass-rebuilds should go via the `staging` branch. It should only see non-breaking commits that are fixing issues blocking it from being merged into the `master ` branch.
241+The `staging-next` branch is for stabilizing mass-rebuilds submitted to the `staging` branch prior to merging them into `master`. Mass-rebuilds must go via the `staging` branch. It must only see non-breaking commits that are fixing issues blocking it from being merged into the `master ` branch.
242242
243243If the branch is already in a broken state, please refrain from adding extra new breakages. Stabilize it for a few days and then merge into master.
244244