Subject: bug#48041: closed (Re: [bug#48041] [PATCH] doc: Clarify the utility of the development branches.)

From: [email-masked] (GNU bug Tracking System)
Date: Mon, 26 Apr 2021 20:14:03 +0000

Your bug report

#48041: [PATCH] doc: Clarify the utility of the development branches.

which was filed against the guix-patches package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
48041: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=48041
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: [bug#48041] [PATCH] doc: Clarify the utility of the development branches.
From: Leo Famulari <[email-masked]>
To: Maxime Devos <[email-masked]>
Cc: [email-masked]
Date: Mon, 26 Apr 2021 16:13:02 -0400
List-Id: <debbugs-submit.debbugs.gnu.org>

On Mon, Apr 26, 2021 at 09:48:42PM +0200, Maxime Devos wrote:
> Leo Famulari schreef op ma 26-04-2021 om 13:51 [-0400]:
> > +(say, @code{gnome-updates}).  This branch is not expected to be
> > +buildable or usable until late in the development process.
> > +6 months or so.  This branch is not expected to be buildable or usable
> > +until late in the development process.
> 
> /me approves

Alright, pushed as 4de688738ce802056dadd6f785c7bdb3407dc768

Subject: [PATCH] doc: Clarify the utility of the development branches.
From: Leo Famulari <[email-masked]>
To: [email-masked]
Date: Mon, 26 Apr 2021 13:51:51 -0400
List-Id: <debbugs-submit.debbugs.gnu.org>

* 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..f28a502338 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 the 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 the development process.
 @end table
 
 All these branches are @uref{@value{SUBSTITUTE-URL},
-- 
2.31.1