Re: js/ci-squelch-doc-warning, was Re: What's cooking in git.git (Feb 2020, #02; Mon, 10)

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 12, 2020, 02:19 UTC
Message-ID: <xmqqk14sv96b.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <nycvar.QRO.7.76.6.2002120036570.3718@tvgsbejvaqbjf.bet>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 18 quoted lines

> On Mon, 10 Feb 2020, Junio C Hamano wrote:
>
>> * js/ci-squelch-doc-warning (2020-02-10) 1 commit
>>  - ci: ignore rubygems warning in the "Documentation" job
>>
>>  Squelch unhelpful warning message during documentation build.
>>
>>  Will merge to 'next'.
>
> To be clear, this _is_ a warning message, but the CI builds are _failing_
> because of it (the "Documentation" job expects `stderr` to be clean except
> for some known warnings).
>
> As a consequence, all the PR builds at https://github.com/git/git are
> failing (except for PRs targeting `pu` or `next`, but I don't think that
> there are currently any).
>
> So maybe we could fast-track this change all the way into `maint`?

Don't worry. As it only affects the doc builds and nothing else, there is no need to rush, but unlike topics that update end-user experience (for which, the minimum gestation periods are 1 day outside 'next' and 7 days in 'next' before hitting 'master'), obvious and trivial docfixes and developer support topics are usually fast-tracked by often immediately hitting 'next' and spending as few as 2 days in 'next'. I think this is one of these topics.