about summary refs log tree commit diff
path: root/doc
diff options
context:
space:
mode:
authorgithub-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>2022-05-18 18:01:13 +0000
committerGitHub <noreply@github.com>2022-05-18 18:01:13 +0000
commit925219f62bae53c1c03be0fbf2617ce40b28af0f (patch)
treea47f734616b113cab0c8f463364375b7a95fe198 /doc
parente7f5c53e02989730f7a9433c417d8076316724d7 (diff)
parent974ba4eaa6e23ba6331ffc6f9a6ec47a23826e27 (diff)
downloadnixlib-925219f62bae53c1c03be0fbf2617ce40b28af0f.tar
nixlib-925219f62bae53c1c03be0fbf2617ce40b28af0f.tar.gz
nixlib-925219f62bae53c1c03be0fbf2617ce40b28af0f.tar.bz2
nixlib-925219f62bae53c1c03be0fbf2617ce40b28af0f.tar.lz
nixlib-925219f62bae53c1c03be0fbf2617ce40b28af0f.tar.xz
nixlib-925219f62bae53c1c03be0fbf2617ce40b28af0f.tar.zst
nixlib-925219f62bae53c1c03be0fbf2617ce40b28af0f.zip
Merge master into staging-next
Diffstat (limited to 'doc')
-rw-r--r--doc/contributing/submitting-changes.chapter.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/contributing/submitting-changes.chapter.md b/doc/contributing/submitting-changes.chapter.md
index d428f00eea56..6f87e015b9cf 100644
--- a/doc/contributing/submitting-changes.chapter.md
+++ b/doc/contributing/submitting-changes.chapter.md
@@ -236,7 +236,7 @@ The `master` branch is the main development branch. It should only see non-break
 
 ### Staging branch {#submitting-changes-staging-branch}
 
-The `staging` branch is a development branch where mass-rebuilds go. It should only see non-breaking mass-rebuild commits. That means it is not to be used for testing, and changes must have been well tested already. If the branch is already in a broken state, please refrain from adding extra new breakages.
+The `staging` branch is a development branch where mass-rebuilds go. Mass rebuilds are commits that cause rebuilds for many packages, like more than 500 (or perhaps, if it's 'light' packages, 1000). It should only see non-breaking mass-rebuild commits. That means it is not to be used for testing, and changes must have been well tested already. If the branch is already in a broken state, please refrain from adding extra new breakages.
 
 ### Staging-next branch {#submitting-changes-staging-next-branch}