From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id wLPYJmvgo2B7ZQAAgWs5BA (envelope-from ) for ; Tue, 18 May 2021 17:42:35 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id gFeSImvgo2A+agAA1q6Kng (envelope-from ) for ; Tue, 18 May 2021 15:42:35 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 46E2415496 for ; Tue, 18 May 2021 17:42:35 +0200 (CEST) Received: from localhost ([::1]:45884 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lj1re-0001sM-CZ for larch@yhetil.org; Tue, 18 May 2021 11:42:34 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:60540) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lj1Mn-0002Fd-PH for guix-devel@gnu.org; Tue, 18 May 2021 11:10:41 -0400 Received: from lepiller.eu ([2a00:5884:8208::1]:55022) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lj1Ml-0001k6-Az; Tue, 18 May 2021 11:10:41 -0400 Received: from lepiller.eu (localhost [127.0.0.1]) by lepiller.eu (OpenSMTPD) with ESMTP id 93e24e84; Tue, 18 May 2021 15:10:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=lepiller.eu; h=date :in-reply-to:references:mime-version:content-type :content-transfer-encoding:subject:to:cc:from:message-id; s= dkim; bh=aJwKGhjWoz0fqa+nEW8rc9X/uJHYCtSCFfBc4ovIb1M=; b=Dpt/CET FoQU66r8RUA59w7jttxxbxne+hpFwjJS52nH+mhV8Wd4J+G2Al7MGEGU8nj9p7bI kGKddcDMNvMuPUuQE9aj9fkex2zEpb6CTFpk80RFWD1h8Xpj9UBTVul7PQvqmE7g OU3XMZ3IOYPb82tC6CPxb3eZyPK1yKHoqSnrou9GnGsP9+wZqBVHZWDCEr8CANE9 mAbBVCnxINeXsu3RIwi51J61A1NxGuk+8DdzM1gCf6KFuhtxRGjqGX4JFpTqfeia OAJAaV9Cr4JeSYSqBzj5nlTne3jRuFH0Qm1HKCG2U0/NcQU0UEAXKg5UWSBbRHPS 9epjt1LwQQmhxLA== Received: by lepiller.eu (OpenSMTPD) with ESMTPSA id 8aeab1fb (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Tue, 18 May 2021 15:10:32 +0000 (UTC) Date: Sun, 16 May 2021 12:47:42 -0400 User-Agent: K-9 Mail for Android In-Reply-To: <87tun2wtsx.fsf@yucca> References: <87eeec8nfc.fsf@gmail.com> <87v97khrse.fsf@gnu.org> <87tun2om0a.fsf_-_@gmail.com> <87tun2wtsx.fsf@yucca> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----UCR3C1AZSR6YNB93JOK6IM8IETEFGD" Content-Transfer-Encoding: 7bit Subject: Re: GNU Guix 1.4.0 in September? (was: Re: GNU Guix 1.3.0 released) To: guix-devel@gnu.org, Vagrant Cascadian , Maxim Cournoyer , =?ISO-8859-1?Q?Ludovic_Court=E8s?= From: Julien Lepiller Message-ID: <50C99522-9DD4-4889-891A-98E83E87AEB3@lepiller.eu> Received-SPF: pass client-ip=2a00:5884:8208::1; envelope-from=julien@lepiller.eu; helo=lepiller.eu X-Spam_score_int: -7 X-Spam_score: -0.8 X-Spam_bar: / X-Spam_report: (-0.8 / 5.0 requ) BAYES_00=-1.9, DATE_IN_PAST_24_48=1.34, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guix-devel Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1621352555; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=qSJQ4CFh36quZr5sXPo1C1aHGoD+56++QY6K5me4t5Q=; b=LsGIKYs1No8/6CRZMd5oloJrwSjNLpohKmhbsa9YFUZGPENa1/f+gP9QGAnUW8q1xR/5HP NwVHlaqh3xY8Yvrs5/jVxcLE+kwRHapUoY+PsNgtpFP2I2hpue5FZkBebNJzPGun17pkd3 jlSFY1RHCIEdD9nGX6bjWVsaxVEiULDsW3W8Pf2nY+z1bHQ0xEzF6g09DAPTL3Y2DRoRL6 XzKwPGgzds3F2IGHiSJ46zUOYGx2ufKdc8ZItqsTM/zKc+XBkansPlhVwDXdZltPyQ1JPz PeniIfTjz+4E4xTNYuSMTD8Lbah7jl5G5ZJZPNe/0xY0e+Sp1jVmi87mL2+jyA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1621352555; a=rsa-sha256; cv=none; b=NTNuUCs/bUc7cd/ZL+BnZw66bF53IMQG0RejAKVONJk/whu1TkMZTELlQGl+wJKME6qxho o5CgT0jRPU9GonJpX8kZlbLTG/rdlHs/yVwv2eis3Ot1L3K2MrO7M9OIM6z4RvIoSwG++1 bE5b6tOb2d+FvRAEvWxOVmXkA9+VrGTM6SwGsuO5f+QTWeT2cE4kzbO5oH7VDv32UNGOTM twsfbI3lSCfjUGSsWcjh8bOPtBBnb+51wF4LpFwU6hsaWlnNU/9hRTtdNPsbzQsn8FQrM8 13djLIbW0Vm6LEgq2YNf0KfpSFveluPHbScZ2Mo1QAzyqFWqwDp2rWdlFPXYRQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=lepiller.eu header.s=dkim header.b="Dpt/CET "; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Migadu-Spam-Score: 1.16 Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=lepiller.eu header.s=dkim header.b="Dpt/CET "; dmarc=fail reason="SPF not aligned (relaxed)" header.from=lepiller.eu (policy=none); spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Migadu-Queue-Id: 46E2415496 X-Spam-Score: 1.16 X-Migadu-Scanner: scn0.migadu.com X-TUID: 3zqLJfJAG71j ------UCR3C1AZSR6YNB93JOK6IM8IETEFGD Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I agree string freeze was way too long for this release=2E We entered strin= g freeze one week before the planned release date, it got pushed by almost = one month=2E For next release, I think it would be better to enter string freeze along = with rc1 or a bit later, but always at least give one week before release (= so a late string freeze could delay release by a few days)=2E Le 16 mai 2021 12:02:38 GMT-04:00, Vagrant Cascadian a =C3=A9crit : >On 2021-05-16, Maxim Cournoyer wrote: >> Yes, thank you Simon and Leo for the help with the release! I felt >less >> lonely :-)=2E I've learned that producing a release can easily take >2-3 >> weeks even in good conditions (e=2Eg=2E, not many blockers to fix)=2E = I'd >> suggest anyone (myself included :-)) trying to meet the schedule to >> seriously start trying to put out RCs a month before the planned >release >> date=2E > >It would be nice to get a Release Candidate (or Pre Release?) out with >some time before the string freeze; it's easiest for me to do the >spelling/grammar/typo checks and fixes after the first RC tarball (as >it >is basically just part of my packaging for Debian workflow), but was a >little disappointing to not be able to get such trivial fixes into the >release=2E > >Alternately or additionally, setting up a "make dist" job on >ci=2Eguix=2Egnu=2Eorg and publishing the resulting tarball somewhere woul= d >allow me to check at arbitrary points during the release cycle and >catch >things earlier=2E > > >live well,=20 > vagrant ------UCR3C1AZSR6YNB93JOK6IM8IETEFGD Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable I agree string freeze was way too long for this re= lease=2E We entered string freeze one week before the planned release date,= it got pushed by almost one month=2E

For next release, I think it w= ould be better to enter string freeze along with rc1 or a bit later, but al= ways at least give one week before release (so a late string freeze could d= elay release by a few days)=2E

Le 16 mai = 2021 12:02:38 GMT-04:00, Vagrant Cascadian <vagrant@debian=2Eorg> a = =C3=A9crit :
On 2021-05-16, Maxim Cournoyer wrote:
Yes, thank you Simon and Leo for the =
help with the release!  I felt less
lonely :-)=2E  I've learned that pro=
ducing a release can easily take 2-3
weeks even in good conditions (e=2E=
g=2E, not many blockers to fix)=2E  I'd
suggest anyone (myself included =
:-)) trying to meet the schedule to
seriously start trying to put out RC=
s a month before the planned release
date=2E

It woul= d be nice to get a Release Candidate (or Pre Release?) out with
some tim= e before the string freeze; it's easiest for me to do the
spelling/gramm= ar/typo checks and fixes after the first RC tarball (as it
is basically = just part of my packaging for Debian workflow), but was a
little disappo= inting to not be able to get such trivial fixes into the
release=2E
<= br>Alternately or additionally, setting up a "make dist" job on
ci=2Egui= x=2Egnu=2Eorg and publishing the resulting tarball somewhere would
allow= me to check at arbitrary points during the release cycle and catch
thin= gs earlier=2E


live well,
vagrant
------UCR3C1AZSR6YNB93JOK6IM8IETEFGD--