From: Leo Famulari <leo@famulari.name>
To: 48041@debbugs.gnu.org
Subject: [bug#48041] [PATCH] doc: Clarify the utility of the development branches.
Date: Mon, 26 Apr 2021 13:51:51 -0400 [thread overview]
Message-ID: <ae6f4bc68574bb381997870514b55681d418b887.1619459511.git.leo@famulari.name> (raw)
* 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
next reply other threads:[~2021-04-26 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 17:51 Leo Famulari [this message]
2021-04-26 19:48 ` [bug#48041] [PATCH] doc: Clarify the utility of the development branches Maxime Devos
2021-04-26 20:13 ` bug#48041: " Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae6f4bc68574bb381997870514b55681d418b887.1619459511.git.leo@famulari.name \
--to=leo@famulari.name \
--cc=48041@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).