me
/
guix
Archived
1
0
Fork 0
Code

doc: Try again to the improve the branching workflow. 

This is a followup to commit 175bea0ca4.

* doc/contributing.texi (Submitting Patches): Distill the workflow to
its essence.
master
Leo Famulari 2021-02-13 13:16:18 -05:00
parent 2a498e9504
commit 58853df8f6
No known key found for this signature in database
GPG Key ID: 2646FA30BACA7F08
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/contributing.texi
View File

@ -1087,11 +1087,11 @@ before they hit users, and to reduce the window during which pre-built
binaries are not available. binaries are not available.
When we decide to start building the @code{staging} or When we decide to start building the @code{staging} or
@code{core-updates} branches, they will be renamed with the suffix @code{core-updates} branches, they will be forked and renamed with the
@code{-frozen}, at which time only bug fixes may be pushed to them. At suffix @code{-frozen}, at which time only bug fixes may be pushed to the
the same time, a corresponding branch suffixed with @code{-next} will be frozen branches. The @code{core-updates} and @code{staging} branches
created to accept patches for the next cycle. Please ask on the mailing will remain open to accept patches for the next cycle. Please ask on
list or IRC if unsure where to place a patch. the mailing list or IRC if unsure where to place a patch.
@c TODO: It would be good with badges on the website that tracks these @c TODO: It would be good with badges on the website that tracks these
@c branches. Or maybe even a status page. @c branches. Or maybe even a status page.