From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Do you plan to release 2.5.2 any time soon?
Date: Fri, 04 Sep 2015 09:08:13 +0200 [thread overview]
Message-ID: <4fe75c9abad6fea816812beba72988fc@dscho.org> (raw)
In-Reply-To: <xmqqbndjjpk5.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On 2015-09-03 21:00, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
>> I have a couple of fixes lined up for bugs in Git for Windows 2.5.1. Do
>> you plan to release 2.5.2 any time soon? If yes, I would hold off,
>> otherwise I will just do a Git for Windows 2.5.1 (Rel 2).
>
> Among the topics marked for possible later merging to 'maint' in the
> draft release notes to 2.6, candidates for future maintenance
> snapshots are:
>
> * mh/get-remote-group-fix # 4 (2 weeks ago)
> * cb/open-noatime-clear-errno # 1 (9 days ago)
> * jk/long-error-messages # 2 (9 days ago)
> * jh/strbuf-read-use-read-in-full # 1 (9 days ago)
> * ps/t1509-chroot-test-fixup # 2 (2 weeks ago)
> * sg/help-group # 1 (8 days ago)
> * nd/dwim-wildcards-as-pathspecs # 1 (9 days ago)
> * jk/fix-alias-pager-config-key-warnings # 1 (3 days ago)
> * jk/rev-list-has-no-notes # 1 (3 days ago)
> * nd/fixup-linked-gitdir # 1 (2 days ago)
> * as/docfix-reflog-expire-unreachable # 1 (8 days ago)
> * sg/t3020-typofix # 1 (8 days ago)
> * po/po-readme # 1 (8 days ago)
> * sg/wt-status-header-inclusion # 1 (8 days ago)
> * ss/fix-config-fd-leak # 1 (8 days ago)
> * jc/calloc-pathspec # 1 (8 days ago)
> * rs/archive-zip-many # 3 (2 days ago)
> * dt/commit-preserve-base-index-upon-opportunistic-cache-tree-update #
> 1 (2 days ago)
> * cc/trailers-corner-case-fix # 3 (22 hours ago)
> * jk/log-missing-default-HEAD # 1 (22 hours ago)
> * ee/clean-test-fixes # 1 (22 hours ago)
>
> These I deem are safe (not just the changes themselves are trivially
> correct but it is unlikely to make things gravely worse if it turns
> out there were ramifications no reviewers thought about with them)
> and can go in 2.5.2.
>
> As to other topics that are in 'master' but not in the above list, I
> do not have doubt about their value (otherwise they would not be in
> 'master' in the first place), but either they are still too young in
> 'master' or are with sufficiently big impact on the callchain that
> it is not entirely implausible that they have risks of unforeseen
> ramifications and fallouts.
>
> Let's aim to tag 2.5.2 soonish, before mid next-week at the latest.
Okay!
Thank you,
Dscho
prev parent reply other threads:[~2015-09-04 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 22:40 Do you plan to release 2.5.2 any time soon? Johannes Schindelin
2015-09-03 19:00 ` Junio C Hamano
2015-09-04 7:08 ` Johannes Schindelin [this message]
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=4fe75c9abad6fea816812beba72988fc@dscho.org \
--to=johannes.schindelin@gmx.de \
--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).