From 1c73a0773caa843fe16ff6e31eb2fcf7c7362695 Mon Sep 17 00:00:00 2001 From: Arnout Engelen Date: Mon, 9 May 2022 12:23:15 +0200 Subject: [PATCH] doc: clarify what a 'mass rebuild' is --- doc/contributing/submitting-changes.chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/contributing/submitting-changes.chapter.md b/doc/contributing/submitting-changes.chapter.md index d428f00eea5..6f87e015b9c 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}