From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>
Cc: "web@dpdk.org" <web@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-web] [PATCH] add release dates template for the year
Date: Tue, 15 Oct 2019 12:58:44 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B07EE3F631@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20191015123543.39966-1-ferruh.yigit@intel.com>
> -----Original Message-----
> From: web [mailto:web-bounces@dpdk.org] On Behalf Of Ferruh Yigit
> Sent: Tuesday, October 15, 2019 1:36 PM
> To: Thomas Monjalon <thomas@monjalon.net>; David Marchand
> <david.marchand@redhat.com>
> Cc: web@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>
> Subject: [dpdk-web] [PATCH] add release dates template for the year
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> content/roadmap/_index.md | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md index
> ef2275c..34dbacd 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -94,6 +94,18 @@ The last period is 1 month long and is dedicated to bug
> fixing.
> - Integration deadline: January 17, 2020
> - Release: February 14, 2020
>
> +#### 20.05
> +
> +- Release: May 2020
> +
> +#### 20.08
> +
> +- Release: August 2020
> +
> +#### 20.11
> +
> +- Release: December 2020
> +
Why December? Should it not be November as usual?
/Bruce
next prev parent reply other threads:[~2019-10-15 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 12:35 Ferruh Yigit
2019-10-15 12:58 ` Richardson, Bruce [this message]
2019-10-15 13:05 ` Ferruh Yigit
2019-10-15 13:28 ` David Marchand
2019-10-15 13:05 ` [dpdk-web] [PATCH v2] " Ferruh Yigit
2019-12-05 14:57 ` 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=59AF69C657FD0841A61C55336867B5B07EE3F631@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
--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).