git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Victoria Dye <vdye@github.com>,
	git-for-windows@googlegroups.com, git@vger.kernel.org
Subject: Re: fixup! bug, was Re: [ANNOUNCE] Git for Windows 2.37.2
Date: Mon, 15 Aug 2022 09:08:18 -0700	[thread overview]
Message-ID: <xmqq35dx4hhp.fsf@gitster.g> (raw)
In-Reply-To: <16r2s842-1r7r-p05n-82o5-q01921r35oqr@tzk.qr> (Johannes Schindelin's message of "Mon, 15 Aug 2022 13:30:20 +0200 (CEST)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> Hi Junio,
>
> On Fri, 12 Aug 2022, Junio C Hamano wrote:
>
>> Victoria Dye <vdye@github.com> writes:
>>
>> > Johannes Schindelin wrote:
>> > Just a heads-up: there was an issue with the process used to generate this
>> > version. ...
>>
>> Sorry to see that it caused two cycles of release process.  Would it
>> have helped you if I had done things differently (other than "not
>> issuing maintenance releases that are not security relevant"), perhaps
>> giving a notice in advance by say a few days?
>
> Thank you for offering to accommodate Git for Windows' needs.
>
> In this instance, we tracked the problem down to ...

Well, I was not asking for postmortem of a particular breakage,
per-se.  Such a bug is well within the competent hands of GfW
developer(s).

I was more interested in learning an improved process, e.g. giving
you an advance notice of a few days so that you can do a practice
run in the not-so-final-but-close-enough tip of the 'maint' branch
to find out unexpected recent breakage either in the code or in your
toolchain before the real release needs to be made in timely
fashion, would have helped.

Thanks.

      reply	other threads:[~2022-08-15 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 21:42 [ANNOUNCE] Git for Windows 2.37.2 Johannes Schindelin
2022-08-11 21:53 ` Junio C Hamano
2022-08-11 23:22 ` Victoria Dye
2022-08-12 16:42   ` Junio C Hamano
2022-08-15 11:30     ` fixup! bug, was " Johannes Schindelin
2022-08-15 16:08       ` Junio C Hamano [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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqq35dx4hhp.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git-for-windows@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=vdye@github.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).