DPDK website maintenance
 help / color / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org
Subject: Re: [dpdk-web] [PATCH 2/2] update 20.08.0 schedule
Date: Mon, 25 May 2020 14:38:38 +0100
Message-ID: <a816da19-c223-a5d7-7be0-6b046d653d4c@intel.com> (raw)
In-Reply-To: <6237533.j30o5G86pd@thomas>

On 5/23/2020 9:15 PM, Thomas Monjalon wrote:
> 22/05/2020 21:53, Ferruh Yigit:
>> As discussed in
>> https://mails.dpdk.org/archives/dev/2020-May/168415.html
>>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>> ---
>>  #### 20.08
>>  
>> -- Release: August 2020
>> +- Proposal deadline: June 12, 2020
>> +- Integration deadline: July 8, 2020
>> +- Release: August 4, 2020
> 
> I prefer wording from the email:
>   * Proposal/V1:		Friday, 12 June 2020
>   * -rc1:			Wednesday, 8 July 2020
>   * -rc2:			Monday, 20 July 2020
>   * Release:		Tuesday, 4 August 2020
> 
> I think -rc2 is an important milestone to plan.
> And -rc1 is less confusing than "integration deadline" which used
> to be a couple of days before -rc1.
> Because all days are not the same, let's write week day.
> 
> I propose these lines:
> 
> - v1 proposal deadline: Friday, 12 June 2020
> - 20.08-rc1: Wednesday, 8 July 2020
> - 20.08-rc2: Monday, 20 July 2020
> - 20.08.0: Tuesday, 4 August 2020
> 
>

LGTM, will send a v2


  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 19:53 [dpdk-web] [PATCH 1/2] update 20.05.0 schedule Ferruh Yigit
2020-05-22 19:53 ` [dpdk-web] [PATCH 2/2] update 20.08.0 schedule Ferruh Yigit
2020-05-23 20:15   ` Thomas Monjalon
2020-05-25 13:38     ` Ferruh Yigit [this message]
2020-05-22 19:58 ` [dpdk-web] [PATCH 1/2] update 20.05.0 schedule Ferruh Yigit
2020-05-25 13:49 ` [dpdk-web] [PATCH v2 " Ferruh Yigit
2020-05-25 13:49   ` [dpdk-web] [PATCH v2 2/2] update 20.08.0 schedule Ferruh Yigit
2020-05-26 16:04     ` Thomas Monjalon

Reply instructions:

You may reply publically 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=a816da19-c223-a5d7-7be0-6b046d653d4c@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

DPDK website maintenance

Archives are clonable:
	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


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.web


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