From 38ab778fbd676fe7f7a84220d0cf7f474573dc2b Mon Sep 17 00:00:00 2001 From: Marius Bakke Date: Sat, 26 May 2018 15:39:13 +0200 Subject: doc: Clarify when branches are "frozen". * doc/contributing.texi (Submitting Patches): Provide a link to Hydra. Add section about freezing branches. --- doc/contributing.texi | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) (limited to 'doc/contributing.texi') diff --git a/doc/contributing.texi b/doc/contributing.texi index 205c972aea..ca44b3b0b0 100644 --- a/doc/contributing.texi +++ b/doc/contributing.texi @@ -407,12 +407,19 @@ changes). This branch is intended to be merged in @code{master} every 2.5 months or so. @end table -All these branches are tracked by our build farm -and merged into @code{master} once +All these branches are @uref{https://hydra.gnu.org/project/gnu, +tracked by our build farm} and merged into @code{master} once everything has been successfully built. This allows us to fix issues before they hit users, and to reduce the window during which pre-built binaries are not available. +Generally, branches other than @code{master} are considered +@emph{frozen} if there has been a recent evaluation, or there is a +corresponding @code{-next} branch. Please ask on 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 branches. Or maybe even a status page. + @item @cindex determinism, of build processes @cindex reproducible builds, checking -- cgit v1.2.3