From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:403:478a::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id QEX+IZ+LGmXc5wAA9RJhRA:P1 (envelope-from ) for ; Mon, 02 Oct 2023 11:21:35 +0200 Received: from aspmx1.migadu.com ([2001:41d0:403:478a::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id QEX+IZ+LGmXc5wAA9RJhRA (envelope-from ) for ; Mon, 02 Oct 2023 11:21:35 +0200 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 D6F4E534B1 for ; Mon, 2 Oct 2023 11:21:34 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=Gt6mO+fb; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1696238495; 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=KaNk97SK/zsFOeWykRwx/6p3Zejl2yWiiTGEQR8HqPE=; b=AQheUKDpWUb7GVK9twnO2Kec4W7Zt9KBMi0jQDC5Yo+GupCzTUomfSXkzSE3ZqrNDAzHCF 9ucR1GpOElfQa7ZQFItKz6gG2pfm2qjm6Rv7sJtD6dbJhVtkYXfkQ2ZtZ+Zlj0cxLTe7/Q EAYJ+/SCOYMY+jw7/CJwn8KBpRBhHh00vsfcjOkzBhVnIn1M3IpnJjwjtX/eT8D6VfyKdt rrgZHxqv/VyYDiDZU4yU/likzyHSLtzgxoWwbOFHqE4EZ9gY0tXS6Mihg0w8xo2/BInbM9 gROFfVIcuZnWTbpG9va+QYWaS/O85OC7oJmbsEz11CiQo1QV4HzmXp7PSSPDag== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1696238495; a=rsa-sha256; cv=none; b=MhpMXnGvmLO2kMRKrqfaOQYI0l1GO05+eSv1emI61bfUhAy/+gsWZ+/X7HmF5uBvkKsSAZ gWKJ1ZE57m6bjt+i0O3YMQb2kt2HYQUqV0Jbz9uuuklpooIN6jXosJZhu2F/hpcEWw9q8H UUxdZ1vfF5DGOyzoePfdwjsXR42AX5rna9e8VpyjhtCNZGyCJ9UIXVsXcHy9KDtaGfrFi4 Wqxn1ii+L5lFBRJL6X1G3VjxLicTHfmUDpJxlpCDXH8+uj8TYYYY0qHpcTsrPPEpNROFVC tjfSVvAMCH1tq5YV5hpD0FXuUYw2HLIellgWoXO+XsMeGjYqqUBi2Q577GCQHg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=Gt6mO+fb; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qnF6j-0004op-Nt; Mon, 02 Oct 2023 05:20:53 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qnF6e-0004oF-LI for guix-devel@gnu.org; Mon, 02 Oct 2023 05:20:50 -0400 Received: from mail-wr1-x434.google.com ([2a00:1450:4864:20::434]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qnF6d-0007gs-1V for guix-devel@gnu.org; Mon, 02 Oct 2023 05:20:48 -0400 Received: by mail-wr1-x434.google.com with SMTP id ffacd0b85a97d-3233799e7b8so1704361f8f.0 for ; Mon, 02 Oct 2023 02:20:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696238445; x=1696843245; darn=gnu.org; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:from:to:cc:subject:date:message-id :reply-to; bh=KaNk97SK/zsFOeWykRwx/6p3Zejl2yWiiTGEQR8HqPE=; b=Gt6mO+fboB1mRLI0htLCZydlaxuf+KiFcdQFSl2KvJPub1X1srjhq1GSKY7Un6OJ8z r5ji41xAFxUs3QEbAm9qWgOIyBIp4rghWU4Z1yfghPAUsqKdeg5707UPDuaojr5Diuf8 YeV6/jvs17I+noJiKsmVEqmD5/nERlzT1VBhp+DsOYZaAeqvqdjbx5ExtCifK5eE18sz 9P+qW1oGRzuhn6FeqFpJTsgYvY5ubiFQexrABH81IjrlHvApdzvvtCXYKffmNndwLxYu JmN7RaPQe4TpJLYa9UdavyTiZSKM87tjHmw8arQP354w7d3/diFdycZwN5ief40RkAtn UIqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696238445; x=1696843245; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=KaNk97SK/zsFOeWykRwx/6p3Zejl2yWiiTGEQR8HqPE=; b=hxjPBHk80pxpzsBVZhpssoSIP+vprDMBp5bYus/I8mNEwDgKJ38OPf5hbN3cOBZPjj XvoGTtb67Sk8oTG41lvujp02dk+5fHPPXu7YwFsP3ZkMUoc6MX7TQaA0NojGyTFhGYKe 0tmNT8QBiJ09gAWpL3x3RtgAE8hdvXGCulhtcjKvalRk/JTpN0G+1GF3bdSB6wzwgm1/ 4AyYh8fRD3QQtEqMim2xxxwdkuorUE4GZvDN48fRJ0sDWkbggM0L5wtMRTMV6BjOrQ0v MfbziO9g+FnM7zrMaOFZ7DcOxwPXddM9130mp7FlaZ4Y0xChh9Qqmz79XMjIa+/AulfO VOCA== X-Gm-Message-State: AOJu0YyzIlZA7XaG4YFQcLAApiGdzv7+sR4VznbyWJKRPPyCXrDbw7wl 3xt1QtDvalQstHqp5z9IeR6Ch5ezqyA= X-Google-Smtp-Source: AGHT+IHUt3gQr84ODrT17zQ8x8329+WeoicMaMDaM3WYwDf+gslHmGddWYfzE2L9zYanKQo3XCZE4w== X-Received: by 2002:a5d:6288:0:b0:317:73e3:cf41 with SMTP id k8-20020a5d6288000000b0031773e3cf41mr8594037wru.1.1696238444902; Mon, 02 Oct 2023 02:20:44 -0700 (PDT) Received: from lili ([2a01:e0a:59b:9120:65d2:2476:f637:db1e]) by smtp.gmail.com with ESMTPSA id u1-20020adfed41000000b003247d3e5d99sm8568476wro.55.2023.10.02.02.20.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 Oct 2023 02:20:44 -0700 (PDT) From: Simon Tournier To: Maxim Cournoyer , Katherine Cox-Buday Cc: Andy Tai , guix-devel@gnu.org Subject: Re: is core-updates still a thing? In-Reply-To: <8734z0291o.fsf@gmail.com> References: <31817bba-f3b0-f4fb-e1b6-97955216232f@gmail.com> <8734z0291o.fsf@gmail.com> Date: Wed, 27 Sep 2023 11:54:05 +0200 Message-ID: <865y3whrgi.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::434; envelope-from=zimon.toutoune@gmail.com; helo=mail-wr1-x434.google.com X-Spam_score_int: 13 X-Spam_score: 1.3 X-Spam_bar: + X-Spam_report: (1.3 / 5.0 requ) BAYES_00=-1.9, DATE_IN_PAST_96_XX=3.405, 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=no autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Scanner: mx0.migadu.com X-Migadu-Spam-Score: -4.36 X-Spam-Score: -4.36 X-Migadu-Queue-Id: D6F4E534B1 X-TUID: PSIJnUXzv1DD Hi, On Tue, 26 Sep 2023 at 12:28, Maxim Cournoyer w= rote: >> My understanding is that feature-branches are now the canonical way to >> work on things, and core-updates has become just another kind of >> feature-branch for landing groups of large changes that don't really >> fit anywhere; the difference being that it's now more ephemeral and >> "as needed" instead of the default for large changes. >> >> Do I have that right? >> >> I guess we need to update the manual? > > I think that's right! It misses a branch for collecting changes with large impact, for instance the ones as sed, grep, ed, etc. Somehow packages that are considered as =E2=80=99core=E2=80=99 but are not part of another team. Rig= ht? Well, from my understanding and for one example, the update of the package Python is managed by the branch python-team but the update of package sed is managed by the branch . I thought this branch is still named core-updates. Well, it could also be staging. Or any other fancy name fitting the feature-branches. :-) IMHO, there is a set of packages that cannot be pushed directly to master and that do not belong to any team. Where are they pushed? And how do we check all is fine with CI/QA before landing them in master? We can create a team (base team?) for that and a dedicated branch (base-team?). IMHO, the easiest was to still consider a core-updates branch collecting changes with large impact and not part of any team; somehow a default branch for these sort of changes. I do not know. Note: it is not related to the core team. :-) It could be but, to my knowledge, it has not been discussed. Cheers, simon