diff mbox series

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

Message ID ae6f4bc68574bb381997870514b55681d418b887.1619459511.git.leo@famulari.name
State Accepted
Headers show
Series [bug#48041] doc: Clarify the utility of the development branches. | expand

Checks

Context Check Description
cbaines/comparison success View comparision
cbaines/git branch success View Git branch
cbaines/applying patch success View Laminar job
cbaines/issue success View issue

Commit Message

Leo Famulari April 26, 2021, 5:51 p.m. UTC 
* 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(-)

Comments

M April 26, 2021, 7:48 p.m. UTC | #1 
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

For the historical record, the corresponding IRC log is at
<http://logs.guix.gnu.org/guix/2021-04-26.log#194041>

Greetings,
Maxime.
Leo Famulari April 26, 2021, 8:13 p.m. UTC | #2 
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
diff mbox series

Patch

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},