From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:52810) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i9uda-0003gO-NU for guix-patches@gnu.org; Mon, 16 Sep 2019 13:18:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i9udW-0008Ns-No for guix-patches@gnu.org; Mon, 16 Sep 2019 13:18:06 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:42158) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i9udW-0008Nk-Kc for guix-patches@gnu.org; Mon, 16 Sep 2019 13:18:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1i9udW-0007nN-EU for guix-patches@gnu.org; Mon, 16 Sep 2019 13:18:02 -0400 Subject: [bug#37413] [PATCH 0/9] Channel news distribution mechanism Resent-Message-ID: References: <20190915221021.4165-1-ludo@gnu.org> <871rwgr3ib.fsf@elephly.net> <87r24g8khp.fsf@gnu.org> <87woe8pej6.fsf@elephly.net> <87k1a86zvd.fsf@gnu.org> From: Ricardo Wurmus In-reply-to: <87k1a86zvd.fsf@gnu.org> Date: Mon, 16 Sep 2019 19:16:50 +0200 Message-ID: <87pnk0p3el.fsf@elephly.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 37413@debbugs.gnu.org Ludovic Court=C3=A8s writes: > Hi, > > Ricardo Wurmus skribis: > >>> Ricardo Wurmus skribis: >>> >>>> Ludovic Court=C3=A8s writes: >>>> >>>>> It=E2=80=99s a bit weird to refer to commits from within a file in th= e repo >>>>> because it almost forces you to push so that you know the commit ID >>>>> that your news entry should refer to. News entries become obsolete >>>>> if you rebase, too. I think it=E2=80=99s acceptable, though. >>>> >>>> Would tags be acceptable instead of commit IDs? I think version tags >>>> would be easier to deal with than commit IDs and it wouldn=E2=80=99t r= equire >>>> time travel as you can just make up a new version and refer to that in >>>> the news file. >>> >>> So you would add a Git tag like =E2=80=9Cnews-xyz=E2=80=9D on the commi= t of interest and >>> then refer to it in the news entry? >> >> No, I actually meant for releases. For a channel it seems to me that a >> release would make sense whenever information must be displayed to the >> users (presumably to announce breaking changes). > > The way I see it, we could use it in between release. I=E2=80=99d have u= sed it > to announce lzip support (and then explain how users can migrate, which > I think many haven=E2=80=99t done because they=E2=80=99re unaware), impro= vements to > =E2=80=98guix pack=E2=80=99, the addition of =E2=80=98guix deploy=E2=80= =99, things like that. > > Does that make sense? I see. Well, I think there=E2=80=99s no harm in pushing the changes first = and then pushing a follow-up commit with the news entry referencing the commit. This all looks good to me. Sure seems useful! -- Ricardo