From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: ferruh.yigit@intel.com, Traynor Kevin <kevin.traynor@intel.com>
Subject: Re: [dpdk-web] [PATCH 2/2] add releases of the year in the roadmap
Date: Sat, 02 Feb 2019 01:41:57 +0100 [thread overview]
Message-ID: <2832938.H1nqiLTI1R@xps> (raw)
In-Reply-To: <20190129174911.6510-2-thomas@monjalon.net>
29/01/2019 18:49, Thomas Monjalon:
> Add empty entries for main and stable 19.xx releases.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> | - | 18.11.1 | January 11, 2019 | November 2020 (LTS) | Kevin Traynor |
> +| - | 19.02.1 | May 31, 2019 | June 2019 | ? |
> +| - | 19.05.1 | August 16, 2019 | September 2019 | ? |
> +| - | 19.08.1 | November 29, 2019 | December 2019 | ? |
Applied with a fixed date for 18.11.1, as discussed with Kevin.
It may be delayed because of the Spring Festival
but it gives a more correct date expectation.
next prev parent reply other threads:[~2019-02-02 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 17:49 [dpdk-web] [PATCH 1/2] release 19.02.0 Thomas Monjalon
2019-01-29 17:49 ` [dpdk-web] [PATCH 2/2] add releases of the year in the roadmap Thomas Monjalon
2019-02-02 0:41 ` Thomas Monjalon [this message]
2019-02-02 0:40 ` [dpdk-web] [PATCH 1/2] release 19.02.0 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=2832938.H1nqiLTI1R@xps \
--to=thomas@monjalon.net \
--cc=ferruh.yigit@intel.com \
--cc=kevin.traynor@intel.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).