From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id EITsH5ASP2PRVQAAbAwnHQ (envelope-from ) for ; Thu, 06 Oct 2022 19:38:24 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id 0LjeH5ASP2ONLwAAauVa8A (envelope-from ) for ; Thu, 06 Oct 2022 19:38:24 +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 38BFD25028 for ; Thu, 6 Oct 2022 19:38:24 +0200 (CEST) Received: from localhost ([::1]:48456 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ogUpD-0007VR-3z for larch@yhetil.org; Thu, 06 Oct 2022 13:38:23 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:42276) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ogTKt-00071n-2E for guix-devel@gnu.org; Thu, 06 Oct 2022 12:03:06 -0400 Received: from lepiller.eu ([2a00:5884:8208::1]:45308) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ogTKo-0004bt-AD; Thu, 06 Oct 2022 12:02:58 -0400 Received: from lepiller.eu (localhost [127.0.0.1]) by lepiller.eu (OpenSMTPD) with ESMTP id 079af18b; Thu, 6 Oct 2022 16:02:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=lepiller.eu; h=date:from :to:cc:subject:in-reply-to:references:message-id:mime-version :content-type:content-transfer-encoding; s=dkim; bh=rL94ETV16mD8 OjlPsLTbFqCB/ae+25fKtgl2Y8Snd78=; b=OhEWGadnpxW6aG9BF+FgJbSFX3NI ZM6g+AA3/v+iF9L7EPVnh/BQJ24/ZMsJwP9mNMgQnel535AVwyETjdtdUlcfmbSG Mwd5YKfyTeLU6PnmJd8bCBZfr5yGjJLtorveYeyBNP0AKlCKhBVFwYhUQQDotJB/ rOwzfL5g/xXvEUROd7WRlwvhM15FCxuS1g/dq3Vde8BzxazPhRMd6L9N6TEfKQTf b/2za8OtFDhDst28O3b/BqSrOAot6gJ37outLue9cpZH75ZGs/gLWcztXp+22LtQ ZWu+kcrGWXkF7tU8SRzmuAfRAOQEL2+vLMCVAopjlyiLiYYkZ9iG8QXqsA== Received: by lepiller.eu (OpenSMTPD) with ESMTPSA id 711bc4ca (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Thu, 6 Oct 2022 16:02:47 +0000 (UTC) Date: Thu, 06 Oct 2022 18:02:47 +0200 From: Julien Lepiller To: =?ISO-8859-1?Q?Ludovic_Court=E8s?= , Guix-devel CC: guix-maintainers@gnu.org, Marius Bakke Subject: Re: Planning for a release, for real User-Agent: K-9 Mail for Android In-Reply-To: <87edvlknv5.fsf@gnu.org> References: <87edvlknv5.fsf@gnu.org> Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=----6ZLQWWW1LUTHYS573MDNIITI9945WB Content-Transfer-Encoding: 7bit Received-SPF: pass client-ip=2a00:5884:8208::1; envelope-from=julien@lepiller.eu; helo=lepiller.eu 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, HTML_MESSAGE=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.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" X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1665077904; 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=lwaQi1ufoL4v9vnARyzaYtT2L6KJXqbj9mIXt/jAupk=; b=gl5QfFdk4bNYPWCllWcfbHb/4JvjZtkn9JstY0toI+7R5+my2JlKgNSYAbb5I0bSF58YP2 v+43nMJ9Qf2YZszovuTePNHeNLVZex0QV3/x06kvBGc6veonO4POZEvu5QE0iH6/0XLqZa o57EIN9Pz1fBOWtm/7sGLO6yA8Utfst4QnMMi0bf5/irkEWppz4QYqgocpoyH4mrR1UTv9 uKT+qWdZcp8g2Rxn8NKgeKIlKnZvx0jpXCfyqj5/kNVhZ78mfrvwICu8XDy/GL1xYVydGI 8+n2Ez8PluwFrepMyhzq4uwAUuFiYAhK50+ea4q1/qSupUiEBKuxlP+8XeqsdQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1665077904; a=rsa-sha256; cv=none; b=XWKtSgBJBhiDorPHNVPKEhG8dpQuoPhH0db2cNMd9Hya3xBOo5jkUhlhMMYxoC2jgw2nZK SVJDDhYDhmlyXdEJy5F8QNBFAPCRrmpH3q9DqqLkNI97w3u7lGi9ufZwdxspJA/Jr/8CNH ZGb6UE0QEfguq77bJGKMXYx5aSGepq10KF+pnUgMxnimCsK2Owty03C6r1V08zKM3sK9A9 7AQwFPeAsF1v4OrNfhEZFApHh6QEJtnUuRaEp6tir2pwZy6QKmu0Lo9Ov1/Gqmpz57X7ab ZOLmezyqIM6LDKv+Vi3R651FoNr58qlmroHEwtAddTJ8C75P6e+tsjtsJNDB0A== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=lepiller.eu header.s=dkim header.b=OhEWGadn; dmarc=pass (policy=none) header.from=lepiller.eu; 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" X-Migadu-Spam-Score: -2.37 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=lepiller.eu header.s=dkim header.b=OhEWGadn; dmarc=pass (policy=none) header.from=lepiller.eu; 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" X-Migadu-Queue-Id: 38BFD25028 X-Spam-Score: -2.37 X-Migadu-Scanner: scn1.migadu.com X-TUID: UuuGYHBhBQzb ------6ZLQWWW1LUTHYS573MDNIITI9945WB Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I'll take care of the cranslations (notifying translators, ensuring string = freeze is respected, =E2=80=A6) We need to be careful not to start the stsing freeze step too early=2E Las= t time (or previous?) we started a week before the scheduled release date, = but the schedule slipped by a few weeks and we had some pressure in the pip= eline because some patches could not be applied because of string changes= =2E Let's try to have a better vision on the planning this time :) Le 6 octobre 2022 16:50:22 GMT+02:00, "Ludovic Court=C3=A8s" a =C3=A9crit=C2=A0: >Hello Guix! > >Will Guix=E2=80=99s 10th year be a release year? I hope so! > >We need to plan and coordinate=2E Releases have to be a group effort; >some of the most important work won=E2=80=99t be coding but coordination= =2E >Coordination is key=2E I don=E2=80=99t think I should be spearheading th= at >effort, but I=E2=80=99m happy to be part of it=2E > >Who=E2=80=99s ready to commit time towards that goal for the coming weeks= ? > >Here=E2=80=99s a list of things to do to get there: > > =E2=80=A2 Merge =E2=80=98staging=E2=80=99 (?)=2E What=E2=80=99s the st= atus of that one, it seemed ready > a couple of weeks ago, but then I lost track of it=2E Marius? > > We need a =E2=80=98staging=E2=80=99 champion to keep track of what=E2= =80=99s left to be > done, reports progress, pings people, etc=2E That person does not > have to be hacking like crazy, on the contrary! > > =E2=80=A2 Get base binaries on all supported architectures in a timely > fashion, or drop some of the architectures=2E > > Namely, =E2=80=98make assert-binaries-available=E2=80=99 is currently= failing=2E It > uses a manifest that encodes what we consider to be the basic > requirements for each architecture; it=E2=80=99s not demanding for > aarch64-linux, even less for armhf-linux and i586-gnu=E2=80=94yet we= =E2=80=99re not > meeting these criteria yet=2E > > We need to look at missing substitutes, address build issues and > build farm issues that cause them until we get to zero failures=2E I= f > after some effort we fail to get to zero, then we should consider > dropping architectures (I=E2=80=99m looking at armhf-linux and i586-g= nu > specifically)=2E > > Again we need a champion to keep track of this and ping people so we > make progress! > > =E2=80=A2 Address the blockers of , most of > which are issues in the installer=2E > > =E2=80=A2 Freeze strings: enter a period where translatable strings in = the > code and in the manual must not be changed so translators have a > chance to keep up=2E Julien, how would you like to do that? Weblate > has given us more flexibility it seems=2E > > =E2=80=A2 Publish a release candidate and call for testing of the insta= ller in > particular=2E Fix bugs, loop=2E > > =E2=80=A2 Update NEWS (mostly done already!), prepare a blog post listi= ng the > highlights and linking to the relevant material=2E (See > for inspiration=2E) > >I=E2=80=99d like us to do this with an eye of getting better organized, w= hich >involves defining roles such as that of =E2=80=9Crelease managers=E2=80= =9D=2E > >The NixOS folks handle this in a way that I find inspiring, with >rotating release manager responsibilities, a schedule announced upfront, >and a detailed description of the process: > > https://github=2Ecom/NixOS/nixpkgs/issues/193585 > https://nixos=2Egithub=2Eio/release-wiki/Home=2Ehtml > >We have > >but it=E2=80=99s low-level and dates back to a time where release were a >one-person activity=2E Time for a change=2E > >So, who=E2=80=99s in? Let=E2=80=99s get our act together! > >Ludo=E2=80=99=2E ------6ZLQWWW1LUTHYS573MDNIITI9945WB Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable I'll take care of the cranslations (notifying tran= slators, ensuring string freeze is respected, =E2=80=A6)

We need to = be careful not to start the stsing freeze step too early=2E Last time (or p= revious?) we started a week before the scheduled release date, but the sche= dule slipped by a few weeks and we had some pressure in the pipeline becaus= e some patches could not be applied because of string changes=2E

Let= 's try to have a better vision on the planning this time :)

Le 6 octobre 2022 16:50:22 GMT+02:00, "Ludovic Court=C3= =A8s" <ludo@gnu=2Eorg> a =C3=A9crit=C2=A0:
Hello Guix!

Will Guix=E2=80=99s =
10th year be a release year?  I hope so!

We need to plan and coordin=
ate=2E  Releases have to be a group effort;
some of the most important w=
ork won=E2=80=99t be coding but coordination=2E
Coordination is key=2E  =
I don=E2=80=99t think I should be spearheading that
effort, but I=E2=80=
=99m happy to be part of it=2E

Who=E2=80=99s ready to commit time to=
wards that goal for the coming weeks?

Here=E2=80=99s a list of thing=
s to do to get there:

  =E2=80=A2 Merge =E2=80=98staging=E2=80=99 (?=
)=2E  What=E2=80=99s the status of that one, it seemed ready
    a coupl=
e of weeks ago, but then I lost track of it=2E  Marius?

    We need =
a =E2=80=98staging=E2=80=99 champion to keep track of what=E2=80=99s left t=
o be
    done, reports progress, pings people, etc=2E  That person does =
not
    have to be hacking like crazy, on the contrary!

  =E2=80=
=A2 Get base binaries on all supported architectures in a timely
    fas=
hion, or drop some of the architectures=2E

    Namely, =E2=80=98make=
 assert-binaries-available=E2=80=99 is currently failing=2E  It
    uses=
 a manifest that encodes what we consider to be the basic
    requiremen=
ts for each architecture; it=E2=80=99s not demanding for
    aarch64-lin=
ux, even less for armhf-linux and i586-gnu=E2=80=94yet we=E2=80=99re not    meeting these criteria yet=2E

    We need to look at missing su=
bstitutes, address build issues and
    build farm issues that cause the=
m until we get to zero failures=2E  If
    after some effort we fail to =
get to zero, then we should consider
    dropping architectures (I=E2=80=
=99m looking at armhf-linux and i586-gnu
    specifically)=2E

   =
 Again we need a champion to keep track of this and ping people so we
  =
  make progress!

  =E2=80=A2 Address the blockers of <https://issues=2Eguix=2Egnu=2Eorg/=
53214>, most of
    which are issues in the installer=2E

 =
 =E2=80=A2 Freeze strings: enter a period where translatable strings in the=

    code and in the manual must not be changed so translators have a    chance to keep up=2E  Julien, how would you like to do that?  Weblate<=
br>    has given us more flexibility it seems=2E

  =E2=80=A2 Publish=
 a release candidate and call for testing of the installer in
    partic=
ular=2E  Fix bugs, loop=2E

  =E2=80=A2 Update NEWS (mostly done alre=
ady!), prepare a blog post listing the
    highlights and linking to the=
 relevant material=2E  (See
    <https://guix=2Egnu=2Eorg/en/blog/tags/releases/=
> for inspiration=2E)

I=E2=80=99d like us to do this with an eye =
of getting better organized, which
involves defining roles such as that =
of =E2=80=9Crelease managers=E2=80=9D=2E

The NixOS folks handle this=
 in a way that I find inspiring, with
rotating release manager responsib=
ilities, a schedule announced upfront,
and a detailed description of the=
 process:

  https://github=2Ecom/NixOS/nixpkgs/issues/193585
  https://nixos=2Egithub=
=2Eio/release-wiki/Home=2Ehtml

We have
<https://git=2Esavannah=2Egnu=2Eorg/cgit/guix/maintenance=2Egit/tree/do=
c/release=2Eorg>
but it=E2=80=99s low-level and dates back to a t=
ime where release were a
one-person activity=2E  Time for a change=2E
So, who=E2=80=99s in?  Let=E2=80=99s get our act together!

Ludo=
=E2=80=99=2E
------6ZLQWWW1LUTHYS573MDNIITI9945WB--