From: David Marchand <david.marchand@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: web@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-web] [PATCH 2/2] add 21.02.0 schedule
Date: Thu, 26 Nov 2020 18:46:47 +0100 [thread overview]
Message-ID: <CAJFAV8zUYXy46+hzidfUQXA+-RWum8NEV_Uaw8jLPmg8_r2crA@mail.gmail.com> (raw)
In-Reply-To: <20201126164429.2585911-2-ferruh.yigit@intel.com>
On Thu, Nov 26, 2020 at 5:44 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>
> Added v21.02 release schedule as finalized in:
> https://mails.dpdk.org/archives/dev/2020-November/193550.html
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> content/roadmap/_index.md | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> index 2956d2c7c440..3aa1a795ff7d 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -100,6 +100,12 @@ The last period is 1 month long and is dedicated to bug fixing.
> - -rc4: November 13, 2020
> - Release: November 27, 2020
>
> +#### 21.02
> +
> +- Proposal deadline (RFC/v1 patches): December 20, 2020
> +- API freeze (-rc1): January 15, 2021
> +- Release: February 5, 2021
> +
> ### Stable Releases {#stable}
> ----
> There is a documentation page describing the
> --
> 2.26.2
>
For the series,
Acked-by: David Marchand <david.marchand@redhat.com>
--
David Marchand
next prev parent reply other threads:[~2020-11-26 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 16:44 [dpdk-web] [PATCH 1/2] update 20.11.0 schedule Ferruh Yigit
2020-11-26 16:44 ` [dpdk-web] [PATCH 2/2] add 21.02.0 schedule Ferruh Yigit
2020-11-26 17:46 ` David Marchand [this message]
2020-11-26 22:11 ` 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=CAJFAV8zUYXy46+hzidfUQXA+-RWum8NEV_Uaw8jLPmg8_r2crA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=ferruh.yigit@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).