From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
Luca Boccassi <bluca@debian.org>,
Yongseok Koh <yskoh@mellanox.com>,
Kevin Traynor <ktraynor@redhat.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: [dpdk-web] [PATCH] clarify current and next stable versions
Date: Fri, 7 Sep 2018 11:41:21 +0100 [thread overview]
Message-ID: <20180907104121.79248-1-ferruh.yigit@intel.com> (raw)
"Next version" column holds already released versions for some releases
and holds next version for some. Also "Date" field is release date
for released ones and planned date for next ones.
Add "current version" column to clarify what is release and what is
next, and remove dates for already released ones converting column to
"Next version date"
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
Cc: Thomas Monjalon <thomas@monjalon.net>
Cc: Luca Boccassi <bluca@debian.org>
Cc: Yongseok Koh <yskoh@mellanox.com>
Cc: Kevin Traynor <ktraynor@redhat.com>
Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>
---
content/roadmap/_index.md | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 166bf4a..e332fcc 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -79,11 +79,11 @@ regression tests are ran, and if clear, the stable release is announced.
Typically a new stable release version follows a mainline release
by 1-2 weeks, depending on the test results.
-| Next version | Date | End of life | Maintainer |
-|---|---|---|---|
-| 16.11.8 | August 14, 2018 | November 2018 (LTS) | Luca Boccassi |
-| 17.11.5 | November 9, 2018 | November 2019 (LTS) | Yongseok Koh |
-| 18.02.2 | June 15, 2018 | June 2018 | Luca Boccassi |
-| 18.05.1 | August 24, 2018 | August 2018 | Christian Ehrhardt |
-| 18.08.1 | November 16, 2018 | November 2018 | Looking for volunteer |
-| 18.11.1 | January 11, 2019 | November 2020 (LTS) | Kevin Traynor |
+| Current version | Next version | Next version Date | End of life | Maintainer |
+|---|---|---|---|---|
+| 16.11.8 | - | - | November 2018 (LTS) | Luca Boccassi |
+| 17.11.4 | 17.11.5 | November 9, 2018 | November 2019 (LTS) | Yongseok Koh |
+| 18.02.2 | - | - | June 2018 | Luca Boccassi |
+| 18.05.1 | - | - | August 2018 | Christian Ehrhardt |
+| - | 18.08.1 | November 16, 2018 | November 2018 | Looking for volunteer |
+| - | 18.11.1 | January 11, 2019 | November 2020 (LTS) | Kevin Traynor |
--
2.17.1
next reply other threads:[~2018-09-07 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 10:41 Ferruh Yigit [this message]
2018-09-07 9:48 ` Luca Boccassi
2018-09-07 9:51 ` Ferruh Yigit
2018-09-07 10:55 ` [dpdk-web] [PATCH v2] " Ferruh Yigit
2018-09-07 9:57 ` Luca Boccassi
2018-10-08 9:41 ` [dpdk-web] [PATCH v3] " Ferruh Yigit
2018-10-08 16:15 ` Yongseok Koh
2018-10-16 8:41 ` Thomas Monjalon
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=20180907104121.79248-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=ktraynor@redhat.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
--cc=yskoh@mellanox.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.
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).