DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	David Marchand <david.marchand@redhat.com>
Cc: John McNamara <john.mcnamara@intel.com>,
	"Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
	"Xu, Qian Q" <qian.q.xu@intel.com>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 21/01/2021
Date: Tue, 26 Jan 2021 09:04:39 +0000
Message-ID: <25d2f419-aed5-6dce-4cdc-68965df4057f@intel.com> (raw)
In-Reply-To: <ce667c92-341e-9b7f-63fe-1c00c69151c5@intel.com>

On 1/21/2021 12:04 PM, Ferruh Yigit wrote:
> Meeting minutes of 21 January 2021
> ----------------------------------


> Release Dates
> -------------
> * v21.02 dates
>    * -rc1 is released on Tuesday, 19 January 2021
>      * http://inbox.dpdk.org/dev/4846307.Pfn0FrbqUJ@thomas/
>    * -rc2                Friday, 29 January 2021
>    * -rc3                Friday, 5 February 2021
>    * Release pushed to   *Wednesday, 17 February 2021*
>    * Release date may conflict with Chinese New Year, we need to discuss and
>      define the release date offline in the mail list, please comment.

Hi all,

Following is the status of the Intel validation team,

If the -rc2 & -rc3 quality is good, the Intel validation team can finish the 
-rc3 testing before holiday starts (11 February) so that release can be done on 
17 February.

If the code changes need to happen after 11 February, or if there are more than 
expected defects on the -rc3 testing, pushing the release to 26 February is the 
safest option to complete all testing after holidays.

Taking into account that -rc3 is on 5 February, this gives us a little time to 
code freeze to make release on 17 February.

      parent reply	other threads:[~2021-01-26  9:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 12:04 Ferruh Yigit
2021-01-22  6:38 ` Ruifeng Wang
2021-01-22 12:11   ` Ananyev, Konstantin
2021-01-26  9:04 ` Ferruh Yigit [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=25d2f419-aed5-6dce-4cdc-68965df4057f@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=thomas@monjalon.net \
    --cc=zhaoyan.chen@intel.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git