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.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS 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 738D41F403 for ; Tue, 18 Oct 2022 17:11:46 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=pobox.com header.i=@pobox.com header.b="fTPDrYq0"; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229769AbiJRRLo (ORCPT ); Tue, 18 Oct 2022 13:11:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50726 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229602AbiJRRLn (ORCPT ); Tue, 18 Oct 2022 13:11:43 -0400 Received: from pb-smtp1.pobox.com (pb-smtp1.pobox.com [64.147.108.70]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AEE07C1495 for ; Tue, 18 Oct 2022 10:11:40 -0700 (PDT) Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 1CAE516466E; Tue, 18 Oct 2022 13:11:38 -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=hfW1YX2zxpYE+BFS3GE9612x4Bgmw+Agxzmn9v JQFvs=; b=fTPDrYq0WuUYoTE/0Q+xy3f8ms3i6r2fcWKO48xKptM3AqUf+X1PAU 5SxFuM/ecfB6GU/V//G8YZ4D3/5tmJ0k9i+pcltrdnjAzkXShgLiiZFYBGyd5DKI ctutZShBj16SZccHB8ZXZcc7UJ1+O/qDmAOmY2kY6cC+K3vMbGAtM= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 05C4716466D; Tue, 18 Oct 2022 13:11:38 -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 3FD4116466C; Tue, 18 Oct 2022 13:11:37 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Glen Choo Cc: Eric DeCosta via GitGitGadget , git@vger.kernel.org, Eric Sunshine , =?utf-8?Q?=C3=86var_Arnfj=C3=B6r=C3=B0_Bjarmason?= , Eric DeCosta , Johannes Schindelin Subject: Re: [PATCH v2 00/12] fsmonitor: Implement fsmonitor for Linux References: Date: Tue, 18 Oct 2022 10:11:36 -0700 In-Reply-To: (Glen Choo's message of "Tue, 18 Oct 2022 10:03:01 -0700") 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: ECB2505C-4F07-11ED-97AD-2AEEC5D8090B-77302942!pb-smtp1.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Glen Choo writes: > I wished we had caught it sooner too. The folks here generally agree > that our weekly release cycle is not ideal for reasons such as this. > Hopefully this is good motivation to move that work forward, though I > can't promise anything right now. It is perfectly OK to have an automated trial build job that runs more frequently than your weekly release cycle, though. It should usually yield only a single bit of usable information (e.g. "there is no 'does not even build from the source' issue in upstream") that may give you assurance (e.g. "if we maintain the course, the next real build for release would hopefully go smoothly"), but when it breaks, you have more time to react. Thanks.