From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE, URIBL_CSS,URIBL_CSS_A shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id 087D91F54E for ; Mon, 15 Aug 2022 16:08:31 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=pobox.com header.i=@pobox.com header.b="Tq55XcK0"; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230264AbiHOQIX (ORCPT ); Mon, 15 Aug 2022 12:08:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57000 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229582AbiHOQIW (ORCPT ); Mon, 15 Aug 2022 12:08:22 -0400 Received: from pb-smtp1.pobox.com (pb-smtp1.pobox.com [64.147.108.70]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 09D561A82F for ; Mon, 15 Aug 2022 09:08:21 -0700 (PDT) Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 4BEFD151D0E; Mon, 15 Aug 2022 12:08:20 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=24U8xPXXy/XbEXECIZPUkDQnsn3mdCLvNoVLlX mzECg=; b=Tq55XcK0qu3+dlVXFUVYHnPCvfQjFwXCkW3sZ/FiiX6N4yuF3Uvjft HxT+ugk1n59wJFWc9aky6Qcmn1JdKVRz0syHgxpl0SRgoTIF0XoUG47XieIjQ0Wp h3I8Y2TBHHuwqM3VCAF6yyjI1ch0b7MrsVtcLT8/JWtRN1RJH3jLU= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 41D7D151D0D; Mon, 15 Aug 2022 12:08:20 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.83.5.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 94B83151D0C; Mon, 15 Aug 2022 12:08:19 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Johannes Schindelin Cc: Victoria Dye , git-for-windows@googlegroups.com, git@vger.kernel.org Subject: Re: fixup! bug, was Re: [ANNOUNCE] Git for Windows 2.37.2 References: <20220811214252.4351-1-johannes.schindelin@gmx.de> <0e859fe2-3f23-4526-083c-082adb0028fc@github.com> <16r2s842-1r7r-p05n-82o5-q01921r35oqr@tzk.qr> Date: Mon, 15 Aug 2022 09:08:18 -0700 In-Reply-To: <16r2s842-1r7r-p05n-82o5-q01921r35oqr@tzk.qr> (Johannes Schindelin's message of "Mon, 15 Aug 2022 13:30:20 +0200 (CEST)") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 7AAE5990-1CB4-11ED-AC64-5E84C8D8090B-77302942!pb-smtp1.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Johannes Schindelin writes: > Hi Junio, > > On Fri, 12 Aug 2022, Junio C Hamano wrote: > >> Victoria Dye 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.