Re: What's cooking in git.git (Nov 2022, #04; Fri, 18)

From: Taylor Blau <me@ttaylorr.com>
Date: Nov 21, 2022, 00:16 UTC
Message-ID: <Y3rDQ3x44BUmmGHV@nand.local>
In-Reply-To: <xmqq35ad181e.fsf@gitster.g>

On Mon, Nov 21, 2022 at 09:10:53AM +0900, Junio C Hamano wrote:

Show 11 quoted lines

> Another question.
>
> Quite a many topics are marked as "Will cook in 'next'".  After we
> go into the pre-release feature freeze period, most topics in 'next'
> are marked as such, and are expected to stay there until the final,
> but as we are yet to tag -rc0, I am a bit puzzled.
>
> Are there concrete exit criteria for them?  Or are they, at this
> very close to -rc0, already judged to be a bit premature for the
> upcoming release so I can safely keep them in 'next' until the
> final?

Anything merged on 2022-11-14 or 2022-11-15 is ready to go to 'master', in my opinion. I held off on integrating them into 'master' on the 18th since they hadn't been in 'next' for that long. Though I think all of those topics are pretty low risk anyway. So I would recommend merging down all of those into 'master' before cutting -rc0 next week.

These are the topics I'd feel comfortable merging down before the release candidate:

 + pw/rebase-no-reflog-action                                   11-09/11-14    #2
 + pw/strict-label-lookups                                      11-10/11-14    #2
 + dd/bisect-helper-subcommand                                  11-11/11-14    #3
 + js/remove-stale-scalar-repos                                 11-11/11-14    #2
 + ab/coccicheck-incremental                                    11-11/11-14   #14
 + kz/merge-tree-merge-base                                     11-12/11-14    #2
 + ab/t7610-timeout                                             11-15/11-15    #2
 + dd/git-bisect-builtin                                        11-15/11-15   #13
 + rp/maintenance-qol                                           11-15/11-15    #4

I also feel comfortable with these (below), but they are newer topics than above. I would like to see at least ps/receive-use-only-advertised in this release, since it saw the most comprehensive review of any of these.

 + mh/gitcredentials-generate                                   11-14/11-18    #1
 + jt/submodule-on-demand                                       11-14/11-18    #1
 + ps/receive-use-only-advertised                               11-17/11-18    #7
 + jk/parse-object-type-mismatch                                11-18/11-18    #2

These ones I am not as sure about, though Ævar (cc'd) will probably try and tell you they're ready to go ;-).

 + ab/cmake-nix-and-ci                                          11-04/11-08   #14
 + ab/submodule-helper-prep-only                                11-08/11-08    #9

Thanks, Taylor