Re: What's cooking in git.git (Mar 2018, #03; Wed, 14)

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 15, 2018, 17:33 UTC
Message-ID: <xmqqk1ud5jmo.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <87r2olenw9.fsf@evledraar.gmail.com>

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

> Given 2.17-rc1 next Tuesday according to your calendar, what's the
> status of these two landing in 2.17?

A rule of thumb for an average topic with just a handful of commits is to stay in 'next' for about a week before graduating. A larger topic with wider implications to the codebase may want to be a few weeks in 'next' (or stay there since before -rc0 and during the feature freeze to the final), while a more trivially correct ones may be there only overnight.

I tend to think that the perl-fixes topic is something we'd rather want to push packgers to try sooner rather than later; there aren't room for "bugs" that affects program execution, but the impact is more to the installation procedure people have around our build procedure.

I do not have a firm opinion on pcre v1 vs v2; the patches are only about flipping the default and not robbing any capabilities from the packagers and the users, so I do not see any need to be unusually careful to merge it down (compared to other topics).