Oleg Pykhalov <go.wigust@gmail.com> writes:

> Hello Mark,
>
> Thank you for explanation of procedure and macro specifications.
> I've pushed ffd526e61ab1b45c6c913ab4e139193e4d5bee9b with a fix.
>
> Also, here is a patch to mention core-updates-next in the documentation.
>
> diff --git a/doc/contributing.texi b/doc/contributing.texi
> index 2792fe2b2..1c33430aa 100644
> --- a/doc/contributing.texi
> +++ b/doc/contributing.texi
> @@ -410,7 +410,8 @@ to be merged in @code{master} every 3 weeks or so.  Topical changes
>  @item more than 1,200 dependent packages
>  @code{core-updates} branch (may include major and potentially disruptive
>  changes).  This branch is intended to be merged in @code{master} every
> -2.5 months or so.
> +2.5 months or so.  Also during official frozen period commits should go
> +to @code{core-updates-next}.
>  @end table

Good idea.  It would be good to clarify that this also applies for
'staging'.  What do you think about this instead?