patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: stable@dpdk.org, bluca@debian.org
Cc: thomas@monjalon.net, ferruh.yigit@intel.com,
	david.marchand@redhat.com, Kevin Traynor <ktraynor@redhat.com>
Subject: [dpdk-stable] [PATCH 2/2] README: add a few notes about a security release
Date: Wed, 13 Nov 2019 16:51:19 +0000	[thread overview]
Message-ID: <20191113165119.10807-2-ktraynor@redhat.com> (raw)
In-Reply-To: <20191113165119.10807-1-ktraynor@redhat.com>

Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
 README | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/README b/README
index a4d7a75..fdf61ab 100644
--- a/README
+++ b/README
@@ -187,4 +187,5 @@ and finally send a patch for the dpdk-web changes to the web team at web@dpdk.or
 
 6-announce-release
+==================
 
 The last step is to announce it. The usage is also simpler: just type the
@@ -194,3 +195,23 @@ too short and simple so far :).
 
 
+
+Security Releases
+=================
+
+Just a reminder any comms to DPDK security team should be over encrypted email.
+
+For releases with embargoed CVEs steps 1/2/3/4 above will be skipped.
+
+Patches will be provided by the DPDK security team. They should be applied
+locally and compile tested locally without using external tools like travis
+that will make the patches public.
+
+For validation notes in step 5, they should be obtained from the author or
+DPDK security team.
+
+In terms of sequence, the main thing is that everyone is ready and available.
+Pushing different tags to the server can be done in series with other stable
+maintainers to avoid any issues with tarball/docs generation. A single website
+update can then be made.
+
 That's all.
-- 
2.21.0


  reply	other threads:[~2019-11-13 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 16:51 [dpdk-stable] [PATCH 1/2] README: add some example links Kevin Traynor
2019-11-13 16:51 ` Kevin Traynor [this message]
2019-11-13 19:27   ` [dpdk-stable] [PATCH 2/2] README: add a few notes about a security release Luca Boccassi
2019-11-13 19:27 ` [dpdk-stable] [PATCH 1/2] README: add some example links Luca Boccassi

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191113165119.10807-2-ktraynor@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=bluca@debian.org \
    --cc=david.marchand@redhat.com \
    --cc=ferruh.yigit@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.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.
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 NNTP newsgroup(s).