Re: What's cooking in git.git (Aug 2018, #04; Fri, 17)

[Jonathan Nieder <jrnieder@gmail.com>]

Hi,

Junio C Hamano wrote:

> Usually, I refrain from merging larger topics in 'next' down to
> 'master' when we get close to -rc0, but I am wondering if it is
> better to merge all of them to 'master', even the ones on the larger
> and possibly undercooked side, expecting that we collectively spend
> effort on hunting and fixing bugs in them during the pre-release
> freeze period.  If we were to go that route, I'd want everybody's
> buy-in and I'll promise to ignore any shiny new toys that appear on
> list that are not regression fixes to topics merged to 'master'
> since the end of the previous cycle to make sure people are not
> distracted.

Based on what I see in 'next' (midx, range-diff, etc), I quite like
this idea.  In private I may still have ideas for new features and
hack away at them but I would avoid sending new feature topics and
would focus on helping polish what's already been sent out.  Let's
make 2.19 easy for people to adopt.

For whatever that's worth.  I'm only one person; others may have their
own wishes.

Thanks,
Jonathan