From: zimoun <zimon.toutoune@gmail.com>
To: "Léo Le Bouter" <lle-bout@zaclys.net>, guix-devel@gnu.org
Subject: Re: Security patching and the branching workflow: a new security-updates branch
Date: Sat, 27 Mar 2021 14:56:59 +0100 [thread overview]
Message-ID: <86k0ps8ztg.fsf@gmail.com> (raw)
In-Reply-To: <aa737bd2b499c7389a5f2c7efdec68e7d8efcc06.camel@zaclys.net>
On Sat, 27 Mar 2021 at 13:42, Léo Le Bouter <lle-bout@zaclys.net> wrote:
> On Sat, 2021-03-27 at 13:29 +0100, zimoun wrote:
>> And as I said elsewhere, “to me, security is important. But it's
>> no less important than everything *else* that is also important!“, so
>> personally I am not convinced that security updates deserve a special
>> treatment compared to a regular update. That’s my opinion. :-)
>
> You can't think this, security updates have prioritized channel of
> distribution in every other GNU/Linux distribution, we in GNU Guix
> created grafts for it, it's not possible to not ship security updates
> promptly, it puts all users at risk.
Oh, I am a big boy and I can think whatever I want! :-)
Kidding aside.
First, what does it mean «risk»? How do you evaluate it? Is it a
relative evaluation or an absolute one?
Second, I am not arguing that security is not important. I am saying
that security is important, as important as everything else that is also
important. What does it mean «important»? How do you evaluate it? Is it a
relative evaluation or an absolute one?
Third, I am aligned with Leo’s words [1]. And probably with yours
too. :-) To me, a better security is not implied by special
treatments for security fixes but instead a better treatment for the
updates in general.
You are proposing a new branch and Chris and I are saying that this
branch already exists and is staging. The real question is to know how
staging currently behaves: how many time between 2 merges? how many
time to rebuild? how many packages are rebuilt between 2 merges? etc.
Is it enough? If not, what could be done to improve? etc.
1: <https://yhetil.org/guix/YFEDt%2FPUd2ZeC6%2FF@jasmine.lan/>
Cheers,
simon
next prev parent reply other threads:[~2021-03-27 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 20:10 Security patching and the branching workflow: a new security-updates branch Léo Le Bouter
2021-03-26 22:13 ` Christopher Baines
2021-03-26 22:30 ` Léo Le Bouter
2021-03-27 8:56 ` Christopher Baines
2021-03-27 12:29 ` zimoun
2021-03-27 12:42 ` Léo Le Bouter
2021-03-27 13:56 ` zimoun [this message]
2021-03-27 14:14 ` Léo Le Bouter
2021-03-30 11:48 ` zimoun
2021-03-31 0:01 ` Léo Le Bouter
2021-03-31 21:29 ` Ludovic Courtès
2021-04-01 12:44 ` Léo Le Bouter
2021-04-01 14:58 ` Ricardo Wurmus
2021-04-01 15:10 ` Léo Le Bouter
2021-04-01 15:42 ` Léo Le Bouter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86k0ps8ztg.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=lle-bout@zaclys.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).