Re: What's cooking in git.git (Feb 2019, #03; Wed, 13)

From: Jeff King <peff@peff.net>
Date: Feb 14, 2019, 05:53 UTC
Message-ID: <20190214055315.GK20578@sigill.intra.peff.net>
In-Reply-To: <xmqqzhqy9axy.fsf@gitster-ct.c.googlers.com>

On Wed, Feb 13, 2019 at 09:49:13PM -0800, Junio C Hamano wrote:

Show 11 quoted lines

> > I'm not worried enough to suggest pulling it back, but it's something we
> > should keep an eye on during the -rc period.
> 
> True.  I actually think that it is probably a good idea to unleash
> this kind of thing as quickly as possible to the real world.  Those
> outside the project, or even inside it, tend to only discover issues
> after a feature release is made, so while I am generally in favor of
> merging a new and potentially disruptive change in an early batch
> after a feature release to 'master' (which would give us enough time
> to fix things up until the next release), I do not think that
> approach would help third-party interop issues very much.

Yeah, I do have the feeling that not many people really exercise our -rc candidates. I'm not sure how to improve that. We could try to push packagers to make them available (and I think Jonathan already does for Debian's "experimental" track). But ultimately I think it is not a packaging/availability question, but just that most people do not bother until there is a real release.

-Peff