From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:c151::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id eDRNBhqTQmAwTgAA0tVLHw (envelope-from ) for ; Fri, 05 Mar 2021 20:22:50 +0000 Received: from aspmx2.migadu.com ([2001:41d0:2:c151::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id qLIlAhqTQmCUEgAA1q6Kng (envelope-from ) for ; Fri, 05 Mar 2021 20:22:50 +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 aspmx2.migadu.com (Postfix) with ESMTPS id 1D33821FA7 for ; Fri, 5 Mar 2021 21:22:49 +0100 (CET) Received: from localhost ([::1]:39764 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lIGyG-0000jQ-8y for larch@yhetil.org; Fri, 05 Mar 2021 15:22:48 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:52064) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lIGy7-0000iL-1Z for guix-devel@gnu.org; Fri, 05 Mar 2021 15:22:39 -0500 Received: from mail-wm1-x334.google.com ([2a00:1450:4864:20::334]:35245) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lIGy4-0003DI-PV for guix-devel@gnu.org; Fri, 05 Mar 2021 15:22:38 -0500 Received: by mail-wm1-x334.google.com with SMTP id m7so2468143wmq.0 for ; Fri, 05 Mar 2021 12:22:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version:content-transfer-encoding; bh=wDrz9W4/WZNJlYvAGnPu5l7kYzp40VNclMhjWrOY974=; b=B46qQ6k1UPQaktTwuiCab9bEqXT0zYEnLO6TSzNJCU5mDqXNK/Th0Mi+zBuecDIBAE fStOCzmgLg6G1QAau1XZPb4cOhf66TbuXV494Fy0QoY5PB2qwhD94BKgGcOnT04XbO+e AVcuheIgGOGt50TB5dhNobP8tSDOq+YTNhmTEY3qHNndAjyZwPPlRu0ufc4zAAXX/JOo 3lFstpP6FZyliLjsKcs/lIb1bbjAmzZ+AGxlKJL95IhOI9JPKSvhEFG9LkRM8uvUX2Cn 4lDl8D7pGfiDh5WlyASgNfkkCVRdFyi6LsBRF03POO4NSaL1HQBUyW/HDMlnQmdhVSaj hUOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version:content-transfer-encoding; bh=wDrz9W4/WZNJlYvAGnPu5l7kYzp40VNclMhjWrOY974=; b=ouTuKAGJRTG3JvbUd0rf7GNJls6lcXD2qefnLdQ/CKk3zm+lJpvZujCSNYQ2mtM33U 1IzGruJ6Pwa93Cl0pUm/URwkI2evmtH4/8NMDBUB9c+6ZhV8rbs9HDGp2TAtEjq33C3w b7HGA+2nT1yMsJ12sez655nClcu87n24ESETauVzUzWbq/4wUslinNcwXiDNxY/+LAVB Qr9ev6vgvzhVbPZPJud1zjVZdoFNtn/gLWgsBSdezmcmuSbflLTyfP5AjStvSqKwhaSt 4OE8da1TIanqgLdPUs5L1rE7Sufuw0lM2Wep26cgchvSx+UjmpOS7fguOlFa76NJAyxm B6Rg== X-Gm-Message-State: AOAM531+B8u6vpMyIbSTZhC/u07GTD6ZQMz1jtq8VJGm/xIGofTDlfyv NrWy+Aq2zpmheU6I+P2WNDGTG22FsGw= X-Google-Smtp-Source: ABdhPJzsN58RIT1mKDw7cTxR548+BW7oJ6Q/NlSxBg+++VYUx6stwI5LLb9yta5qu+S3QF9Whh10xw== X-Received: by 2002:a1c:2e58:: with SMTP id u85mr10264424wmu.71.1614975754942; Fri, 05 Mar 2021 12:22:34 -0800 (PST) Received: from lili ([2a01:e0a:59b:9120:65d2:2476:f637:db1e]) by smtp.gmail.com with ESMTPSA id z2sm7107531wrm.0.2021.03.05.12.22.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 05 Mar 2021 12:22:34 -0800 (PST) From: zimoun To: Leo Famulari , Andreas Enge Subject: Re: Release on April 18th? In-Reply-To: References: Date: Fri, 05 Mar 2021 21:20:10 +0100 Message-ID: <86im65s685.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2a00:1450:4864:20::334; envelope-from=zimon.toutoune@gmail.com; helo=mail-wm1-x334.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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: -2.06 Authentication-Results: aspmx2.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=B46qQ6k1; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx2.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: 1D33821FA7 X-Spam-Score: -2.06 X-Migadu-Scanner: scn1.migadu.com X-TUID: tXH6HwYNJixY Hi, On Fri, 05 Mar 2021 at 14:27, Leo Famulari wrote: > On Fri, Mar 05, 2021 at 03:31:22PM +0100, Andreas Enge wrote: >> it would be nice if core-updates could be part of the release. I have >> been waiting for gmp, mpfr and mpc to appear in master. In particular >> mpfr-4.1.0 has been released in July 2020, and I have updated it in >> core-updates in the same month. Even with a release in April, that makes >> 9 months! Otherwise, we would end very far off the 6 months suggested in >> doc/contributing.texi. >>=20 >> If I read the git history correctly, we have merged core-updates for the >> last time in May 2020. Shocking numbers. Hopefully the recent progress >> in continuous integration will help us reach our goal of more frequent >> merging again. > > I agree, it's a long time without core-updates. Guix could complete > core-updates in time for April 18, at least for x86_64, if many people > work on it. 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: > 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. 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. In my views, since Guix is a rolling release, adding tags is more about public announcement than =E2=80=9Cfeatures=E2=80=9C, i.e., attract users an= d communicate about the new stuff. Therefore, merging core-updates before a release could be cool because it increases the list of new stuff but this merge is not mandatory. Once the user is in, =E2=80=99guix pull=E2=80=99 provide= s what is in core-updates whenever the merge is. And what is in core-updates will be advertised at the next release (~6 months later). (Releasing every ~3 months should be even better but we do not have the task force to make it.) That=E2=80=99s said, when could core-update be merged to master? What coul= d 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? Cheers, simon