From 4de688738ce802056dadd6f785c7bdb3407dc768 Mon Sep 17 00:00:00 2001 From: Leo Famulari Date: Mon, 26 Apr 2021 13:50:19 -0400 Subject: doc: Clarify the utility of the development branches. * doc/contributing.texi (Submitting Patches): Clarify the utility of the 'staging' and 'core-updates' branches. --- doc/contributing.texi | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/contributing.texi b/doc/contributing.texi index d5025dd189..0a39aa89d6 100644 --- a/doc/contributing.texi +++ b/doc/contributing.texi @@ -1080,12 +1080,14 @@ rebuilding induced, commits go to different branches, along these lines: @code{staging} branch (non-disruptive changes). This branch is intended to be merged in @code{master} every 6 weeks or so. Topical changes (e.g., an update of the GNOME stack) can instead go to a specific branch -(say, @code{gnome-updates}). +(say, @code{gnome-updates}). This branch is not expected to be +buildable or usable until late in its development process. @item more than 1,800 dependent packages @code{core-updates} branch (may include major and potentially disruptive changes). This branch is intended to be merged in @code{master} every -6 months or so. +6 months or so. This branch is not expected to be buildable or usable +until late in its development process. @end table All these branches are @uref{@value{SUBSTITUTE-URL}, -- cgit v1.2.3