DPDK website maintenance
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, <web@dpdk.org>
Subject: Re: [PATCH] update 21.11.0 schedule
Date: Thu, 11 Nov 2021 09:29:39 +0000	[thread overview]
Message-ID: <dd2c1797-80fa-ac00-b78f-d203cfa8b9b5@intel.com> (raw)
In-Reply-To: <20211111091840.2716847-1-thomas@monjalon.net>

On 11/11/2021 9:18 AM, Thomas Monjalon wrote:
> -rc2 was released on Monday (instead of last Friday).
> As discussed in the maintainers meeting,
> -rc3 should be on Tuesday to allow more fixes.
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> Already applied to quickly update the web page
> as agreed in maintainers meeting.
> ---
>   content/roadmap/_index.md | 5 +++--
>   1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> index 36aecdd..ef0da71 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -111,8 +111,9 @@ The last period is 1 month long and is dedicated to bug fixing.
>   
>   - Proposal deadline (RFC/v1 patches): 10 September 2021
>   - API freeze (-rc1): 25 October 2021
> -- PMD features freeze (-rc2): 5 November 2021
> -- Builtin applications features freeze (-rc3): 12 November 2021
> +- PMD features freeze (-rc2): 8 November 2021
> +- Builtin applications features freeze (-rc3): 16 November 2021
> +- Last release candidate (-rc4): 22 November 2021
>   - Release: 24 November 2021
>   
>   ### Stable Releases {#stable}
> 

Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

  reply	other threads:[~2021-11-11  9:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11  9:18 Thomas Monjalon
2021-11-11  9:29 ` Ferruh Yigit [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-28  9:45 Thomas Monjalon
2021-10-28  9:58 ` Mcnamara, John
2021-10-28 16:24   ` Ajit Khaparde

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=dd2c1797-80fa-ac00-b78f-d203cfa8b9b5@intel.com \
    --to=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).