Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes:
> In your previous kitchen status ("What's cooking") you hinted at a
> possible v2.10.1 soon. I have a couple of bugfixes lined up for Git for
> Windows and would like to avoid unnecessarily frequent release
> engineering... Any more concrete ideas on a date for this version?
I scanned RelNotes for 2.11 and identified these topics that we'd
want to have in 'maint'.
bw/pathspec-remove-unused-extern-decl # 1 (6 days ago)
rs/checkout-some-states-are-const # 1 (6 days ago)
rs/strbuf-remove-fix # 1 (6 days ago)
rs/unpack-trees-reduce-file-scope-global # 1 (6 days ago)
mr/vcs-svn-printf-ulong # 1 (6 days ago)
sy/git-gui-i18n-ja # 7 (12 days ago)
jk/fix-remote-curl-url-wo-proto # 1 (12 days ago)
js/git-gui-commit-gpgsign # 2 (12 days ago)
jk/patch-ids-no-merges # 2 (6 days ago)
ew/http-do-not-forget-to-call-curl-multi-remove-handle # 3 (6 days ago)
rs/xdiff-merge-overlapping-hunks-for-W-context # 1 (6 days ago)
ks/perf-build-with-autoconf # 1 (6 days ago)
jt/format-patch-base-info-above-sig # 1 (6 days ago)
jk/rebase-i-drop-ident-check # 1 (6 days ago)
jk/reduce-gc-aggressive-depth # 1 (6 days ago)
et/add-chmod-x # 1 (6 days ago)
tg/add-chmod+x-fix # 7 (24 hours ago)
Most are internal clean-ups that I do not mind leaving out, but I
think we want to have that "add --chmod=+x" fix in. As it hasn't
been enough time passed since the topic was merged to 'master', I'd
say either
(1) 2.10.1 with everything other than the last two in a few days
and 2.10.2 late next week with "add --chmod=+x" fix, or
(2) just a single 2.10.1 with everything late next week.
I can go either way and welcome suggestions. I'd start merging
older topics in the above list to 'maint' soonish, but not today.
Thanks.