Re: What's cooking in git.git (Nov 2013, #05; Thu, 21)

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 22, 2013, 20:05 UTC
Message-ID: <xmqqr4a8yzga.fsf@gitster.dls.corp.google.com>
In-Reply-To: <CAFFjANQy72zLuxtpA+-nMhYEt=qfOu_FSszR8X7QNPTKBEi6tA@mail.gmail.com>

Vicent Martí <tanoku@gmail.com> writes:

Show 8 quoted lines

> On Fri, Nov 22, 2013 at 8:36 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
> We are running a slightly older version of the patchset, because we're
> still on 1.8.4 and the current reroll doesn't apply cleanly there.
>
> If this could make it to `next` some time next week, that would work
> out great for us, because we may start considering using `next` as a
> partial or full deployment on our production machines

I do not think potentially incompatible stuff that are slated for 2.0 that have been cooking in 'next' affects the server side, so that may be a good and safe move.

> This also means that we could exercise the patchset and everything
> else that is queued up in next release...

There is no 'next release' though; there is no guarantee what is cooking in 'next' will be in any future release ;-).

In any case, it is nice to see that people from a large hosting site finally taking a hint from my occasional light complaints that come after "thanks for reporting" whenever I see regression and breakage report soon after a topic graduates to 'master' ;-). It is good to see that more people starting to adopt the 'next' branch early for wider testing.

Thanks.