From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id OLpRIJqbQmDuHQAA0tVLHw (envelope-from ) for ; Fri, 05 Mar 2021 20:59:06 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id cFQzHJqbQmC6UAAAB5/wlQ (envelope-from ) for ; Fri, 05 Mar 2021 20:59:06 +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 2D868CE99 for ; Fri, 5 Mar 2021 21:59:06 +0100 (CET) Received: from localhost ([::1]:57550 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lIHXN-0005Dl-8L for larch@yhetil.org; Fri, 05 Mar 2021 15:59:05 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:33442) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lIHXB-0005Bt-N2 for guix-devel@gnu.org; Fri, 05 Mar 2021 15:58:53 -0500 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]:38559) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lIHX9-00057t-Ir for guix-devel@gnu.org; Fri, 05 Mar 2021 15:58:53 -0500 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 8511E2A40; Fri, 5 Mar 2021 15:58:49 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 05 Mar 2021 15:58:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=famulari.name; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-transfer-encoding:in-reply-to; s=mesmtp; bh=5LhVsyZ2p8pFliEoRvciWGd1AP8PLvWtrgxjdUn4JNA=; b=z7dyxJYT8TjF wBQhAYAH3BwBx2Xagk/SWZOGZUsZ5ePW8LIqRpMN4CPctUjVt7c0TyyDSo/MtcGz NkffvTgv9R5DOKYUfgh7F7/N7qfhftNEMo5vm0zSdLvj7zlD19ttb9/QSGhR6HRN h51Z0ZaqXkDQX8t6/g59EaDcjQFbXq0= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=5LhVsyZ2p8pFliEoRvciWGd1AP8PLvWtrgxjdUn4J NA=; b=MEM8mrcY1B1iOHKQ/VAXFigBEn4J6hzlhuCpBD6SVt4WfDuUPaOwoP9Jh gHuUP8nO6j9/RiQsG9ZBGSgbDXqREICUiQcI0wt7+mQp1Mc8NjRinGol/PsJZi/i tP9Rahz9soo2D+cXgpp21Tq9ZjliRMo/+QVHg7Ije5QTeiltQBNQWtqCs0G9+Kv7 f23x68fInUGgJcb6OGAjydcyXZDQi3dGzc6zEhAIz6WNmKlzTqnnjKtQJR7SPrM+ 9u4vZsFNmOXdbjbEOkJs0bBJoWsXdd3FkvWYA1E45FBnEmsDKGxLesc7GfhX+fr0 aDl5ptSok84VOEcZ6qf7noPnh9tJw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledruddtiedgudefvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvuffkfhggtggugfgjsehtkeertddttdejnecuhfhrohhmpefnvgho ucfhrghmuhhlrghrihcuoehlvghosehfrghmuhhlrghrihdrnhgrmhgvqeenucggtffrrg htthgvrhhnpefgudffteettdekkeduhffgfefgieefgeeuieetudejffelieduueeifffg udfgudenucffohhmrghinhepghhnuhdrohhrghenucfkphepuddttddruddurdduieelrd duudeknecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep lhgvohesfhgrmhhulhgrrhhirdhnrghmvg X-ME-Proxy: Received: from localhost (pool-100-11-169-118.phlapa.fios.verizon.net [100.11.169.118]) by mail.messagingengine.com (Postfix) with ESMTPA id 4B415240054; Fri, 5 Mar 2021 15:58:48 -0500 (EST) Date: Fri, 5 Mar 2021 15:58:46 -0500 From: Leo Famulari To: zimoun Subject: Re: Release on April 18th? Message-ID: References: <86im65s685.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <86im65s685.fsf@gmail.com> Received-SPF: pass client-ip=64.147.123.24; envelope-from=leo@famulari.name; helo=wout1-smtp.messagingengine.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham 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 X-Migadu-Spam-Score: -0.36 Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=famulari.name header.s=mesmtp header.b=z7dyxJYT; dkim=fail ("headers rsa verify failed") header.d=messagingengine.com header.s=fm2 header.b=MEM8mrcY; dmarc=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: 2D868CE99 X-Spam-Score: -0.36 X-Migadu-Scanner: scn0.migadu.com X-TUID: tHSQcKvF4vtX On Fri, Mar 05, 2021 at 09:20:10PM +0100, zimoun wrote: > On #guix, I proposed [1] without an answer (yet :-)): > > what is the current blocking for merging core-updates? I mean > the last merge seems from May 2020. If all the branch is not in > a state to be mergeable, maybe we could simply merge a part of > it. WDYT? > > 1: Anything is possible, but I think that determining which parts are ready to merge will be just as much work as completing the entire branch. Unless people have been maintaining private branches with specific updates cherry-picked and can vouch that they are working well. > On Fri, 05 Mar 2021 at 14:27, Leo Famulari wrote: > > Simon, is there a reason you chose April 18 for the release? Or could we > > choose a later date? > > Because a) it is ~6 months later than previous one and I think releasing > twice a year is the process we should adopt, b) it is an anniversary > (first commit) and by chance the other anniversary (first public > announce on Nov. 23rd) is spaced by ~6 month. Agreed. > However, I think it is a bad idea to postpone and wait for core-updates > merge. We should fix deadlines for releasing everything ~6 months and > simply make it happen. IMHO. Agreed. But I don't think we can force core-updates, or we will regret it when problems slip through. It's better to release on schedule without core-updates. > That’s said, when could core-update be merged to master? What could be > the deadline? From my point of view, delaying a couple (meaning 2 or 3 > here ;-)) of weeks from April 18th sounds fine with me. > > Even, from my understanding, we should minor release ASAP, e.g., on > April 18th or even before if possible. And we could also plan to > release (major or minor) after the core-updates merge (say in June). > Then on Nov. 23rd, I think it could be nice to have another release. > Well, since Guix is rolling-release, releasing should be smooth. > > BTW, I sympathize with the frustration about core-updates not merged > since last May. On the other hand, I did nothing to help in the merging > process. :-( Maybe, we could organize a hackathon or synchronize a > core-updates week: freeze the branch and address issues. WDYT? So, based on the status of ci.guix.gnu.org, I feel that we could not have begun working on core-updates before January 2021. And then, in January, staging was in progress. Now, ci.guix.gnu.org is working well, and we can work more quickly and confidently. However, my experience in the past tells me that 6 weeks is not quite long enough to complete the branch and validate it for a release. But, it really depends on how many people can help.