From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
zimoun <zimon.toutoune@gmail.com>,
guix-devel@gnu.org
Subject: Re: Security patching and the branching workflow: a new security-updates branch
Date: Thu, 01 Apr 2021 17:42:23 +0200 [thread overview]
Message-ID: <db4b11082497b863e0fa29daf432c4494f60a749.camel@zaclys.net> (raw)
In-Reply-To: <87blay2gsj.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
Sorry for duplicated email,
On Thu, 2021-04-01 at 16:58 +0200, Ricardo Wurmus wrote:
> I don’t think we should have a security-updates
> branch, because the role of that branch is effectively taken by
> staging.
I don't think that's the case because staging is documented for things
that do not make too many rebuilds (in which case they'd go to core-
updates), and some times security updates do cause rebuilds in the
1800+ and they could not go through staging. The proposed security-
updates branch would not have that limitation. We could of course also
revisit the policy for staging and prioritize security updates through
that branch while also committing to actually merging that branch on
schedule.
Léo
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-04-01 15:42 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
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 [this message]
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=db4b11082497b863e0fa29daf432c4494f60a749.camel@zaclys.net \
--to=lle-bout@zaclys.net \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@gmail.com \
/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).