From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: web@dpdk.org
Cc: Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <luca.boccassi@microsoft.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: [dpdk-web] [PATCH] update LTS ownership
Date: Wed, 27 Jan 2021 16:51:35 +0100 [thread overview]
Message-ID: <20210127155135.3730352-1-christian.ehrhardt@canonical.com> (raw)
I was told that Kevin (thanks to all the great work!) wanted to step
back of the 20.11 LTS maintenance.
In a discussion Luca and I agreed that I can take over the further
19.11.x (as that is what we use in Ubuntu 20.04 LTS) and he would
in return take 20.11.x (which will be what is in the coming Debian
release).
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
---
content/roadmap/_index.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 132da1c..06ebcb0 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -124,5 +124,5 @@ by 1-2 weeks, depending on the test results.
| Current version | Next version | Next version Date | End of life | Maintainer |
|----------|----------|-------------------|---------------------|--------------------|
| 18.11.11 | - | - | December 2020 (EOL) | - |
-| 19.11.6 | 19.11.7 | March 2021 | November 2021 (LTS) | Luca Boccassi |
-| - | 20.11.1 | March 2021 | November 2022 (LTS) | Kevin Traynor |
+| 19.11.6 | 19.11.7 | March 2021 | November 2021 (LTS) | Christian Ehrhardt |
+| - | 20.11.1 | March 2021 | November 2022 (LTS) | Luca Boccassi |
--
2.30.0
next reply other threads:[~2021-01-27 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 15:51 Christian Ehrhardt [this message]
2021-01-27 15:55 ` Luca Boccassi
2021-01-27 16:18 ` Thomas Monjalon
2021-01-27 17:11 ` Kevin Traynor
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=20210127155135.3730352-1-christian.ehrhardt@canonical.com \
--to=christian.ehrhardt@canonical.com \
--cc=ktraynor@redhat.com \
--cc=luca.boccassi@microsoft.com \
--cc=web@dpdk.org \
/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).