me
/
guix
Archived
1
0
Fork 0
Code

doc: Clarify the utility of the development branches. 

* doc/contributing.texi (Submitting Patches): Clarify the utility of the
'staging' and 'core-updates' branches.
master
Leo Famulari 2021-04-26 13:50:19 -04:00
parent bd3f3f8150
commit 4de688738c
No known key found for this signature in database
GPG Key ID: 2646FA30BACA7F08
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/contributing.texi
View File

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