git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Taylor Blau" <me@ttaylorr.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2022, #04; Fri, 18)
Date: Sun, 20 Nov 2022 19:16:03 -0500	[thread overview]
Message-ID: <Y3rDQ3x44BUmmGHV@nand.local> (raw)
In-Reply-To: <xmqq35ad181e.fsf@gitster.g>

On Mon, Nov 21, 2022 at 09:10:53AM +0900, Junio C Hamano wrote:
> 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

  reply	other threads:[~2022-11-21  0:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19  2:22 What's cooking in git.git (Nov 2022, #04; Fri, 18) Taylor Blau
2022-11-20 11:24 ` SZEDER Gábor
2022-11-20 17:42 ` Looking for a review (pretty-formats, hard truncation), was What's cooking in git.git (Nov 2022, #04; Fri, 18)) Philip Oakley
2022-11-21  0:37   ` Junio C Hamano
2022-11-21 18:10     ` Philip Oakley
2022-11-20 19:46 ` What's cooking in git.git (Nov 2022, #04; Fri, 18) Phillip Wood
2022-11-20 21:24   ` Johannes Schindelin
2022-11-21  0:47     ` Junio C Hamano
2022-11-21  1:00       ` Taylor Blau
2022-11-22 14:58     ` Phillip Wood
2022-11-20 21:45 ` Junio C Hamano
2022-11-20 23:51   ` Taylor Blau
2022-11-20 23:24 ` Junio C Hamano
2022-11-20 23:52   ` Taylor Blau
2022-11-21  3:36     ` Junio C Hamano
2022-11-22 22:56       ` Taylor Blau
2022-11-21  0:10 ` Junio C Hamano
2022-11-21  0:16   ` Taylor Blau [this message]
2022-11-23  0:03     ` Junio C Hamano
2022-11-21 22:22 ` ab/submodule-no-abspath (was Re: What's cooking in git.git (Nov 2022, #04; Fri, 18)) Glen Choo
2022-11-22 22:45   ` [PATCH] submodule absorbgitdirs: use relative <from> and <to> paths Ævar Arnfjörð Bjarmason
2022-11-23  0:43     ` Glen Choo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y3rDQ3x44BUmmGHV@nand.local \
    --to=me@ttaylorr.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).