DPDK website maintenance
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, <john.mcnamara@intel.com>,
	<david.marchand@redhat.com>, <jerinj@marvell.com>,
	<maxime.coquelin@redhat.com>, <ajit.khaparde@broadcom.com>,
	<gakhil@marvell.com>
Cc: <web@dpdk.org>
Subject: Re: [PATCH] update 22.03.0 schedule
Date: Mon, 7 Feb 2022 13:25:26 +0000
Message-ID: <8176cf15-4572-0f1d-83d1-181a19ba8d51@intel.com> (raw)
In-Reply-To: <5791629.lOV4Wx5bFT@thomas>

On 2/7/2022 1:21 PM, Thomas Monjalon wrote:
> 03/02/2022 14:25, Thomas Monjalon:
>> 03/02/2022 12:18, Ferruh Yigit:
>>> 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.
>>
>> Indeed we did not clarify the impact on -rc2 and -rc3 in the meeting.
>> I think we should keep the same amount of time for -rc2 and -rc3,
>> and squeeze in the last week before the release.
>> Opinions?
>>
>>>> -- 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
> 
> Do we agree on these dates?
> 
> 

OK for me,
I am for merging ASAP so community can be aware of the -rc1 date change.

  reply	other threads:[~2022-02-07 13:25 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
2022-02-03 13:25   ` Thomas Monjalon
2022-02-07 13:21     ` Thomas Monjalon
2022-02-07 13:25       ` Ferruh Yigit [this message]
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=8176cf15-4572-0f1d-83d1-181a19ba8d51@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=david.marchand@redhat.com \
    --cc=gakhil@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=maxime.coquelin@redhat.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

DPDK website maintenance

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/web/0 web/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 web web/ http://inbox.dpdk.org/web \
		web@dpdk.org
	public-inbox-index web

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.web


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