From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, <web@dpdk.org>
Cc: <john.mcnamara@intel.com>, <david.marchand@redhat.com>
Subject: Re: [PATCH] update 22.03.0 schedule
Date: Thu, 3 Feb 2022 11:18:04 +0000 [thread overview]
Message-ID: <1796ffb7-627f-1dcb-b0b7-c816e106f1ae@intel.com> (raw)
In-Reply-To: <20220203110925.1639700-1-thomas@monjalon.net>
On 2/3/2022 11:09 AM, Thomas Monjalon wrote:
> As discussed in the maintainers meeting,
> the release candidates are pushed by 2 days.
>
Only -rc1 date was discussed, but do you think will it have
knock-on effect to other release candidates?
No objection from my end, just asking to clarify.
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> content/roadmap/_index.md | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> index 9d3f8e6..9d372c8 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -95,9 +95,9 @@ The last period is approximately 1 month long and is dedicated to bug fixing.
> #### 22.03
>
> - Proposal deadline (RFC/v1 patches): 31 December 2021
> -- API freeze (-rc1): 9 February 2022
> -- PMD features freeze (-rc2): 23 February 2022
> -- Builtin applications features freeze (-rc3): 2 March 2022
> +- API freeze (-rc1): 11 February 2022
> +- PMD features freeze (-rc2): 25 February 2022
> +- Builtin applications features freeze (-rc3): 4 March 2022
> - Release: 11 March 2022
>
> #### 22.07
next prev parent reply other threads:[~2022-02-03 11:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 11:09 Thomas Monjalon
2022-02-03 11:18 ` Ferruh Yigit [this message]
2022-02-03 13:25 ` Thomas Monjalon
2022-02-07 13:21 ` Thomas Monjalon
2022-02-07 13:25 ` Ferruh Yigit
2022-02-07 13:31 ` Thomas Monjalon
2022-02-07 13:42 ` [EXT] " Akhil Goyal
2022-03-11 7:19 Thomas Monjalon
2022-03-11 7:43 ` Mcnamara, John
2022-03-14 7:53 ` 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=1796ffb7-627f-1dcb-b0b7-c816e106f1ae@intel.com \
--to=ferruh.yigit@intel.com \
--cc=david.marchand@redhat.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).