From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"O'Hare, Cathal" <cathal.ohare@intel.com>,
"asafp@mellanox.com" <asafp@mellanox.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"hemant.agrawal@oss.nxp.com" <hemant.agrawal@oss.nxp.com>,
"honnappa.nagarahalli@arm.com" <honnappa.nagarahalli@arm.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
"arybchenko@solarflare.com" <arybchenko@solarflare.com>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 14/05/2020
Date: Thu, 21 May 2020 08:28:40 +0000 [thread overview]
Message-ID: <DM6PR11MB2537B3DFF099A1E5FD85E37DEFB70@DM6PR11MB2537.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2215007.3c9HiEOlIg@thomas>
Hi Thomas,
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Thomas Monjalon
> Sent: Friday, May 15, 2020 5:14 PM
> To: dev@dpdk.org
> Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>; O'Hare, Cathal <cathal.ohare@intel.com>;
> asafp@mellanox.com; jerinj@marvell.com; hemant.agrawal@oss.nxp.com;
> honnappa.nagarahalli@arm.com; david.marchand@redhat.com;
> ajit.khaparde@broadcom.com; arybchenko@solarflare.com
> Subject: Re: [dpdk-dev] DPDK Release Status Meeting 14/05/2020
>
> Hi,
>
> Please let's discuss the dates for the next release cycle.
>
> > * v20.08 proposal dates, please comment:
> > * Proposal/V1: Tuesday, 16 June 2020
> > * Integration/Merge/RC1: Tuesday, 14 July 2020
> > * Release: Friday, 7 August 2020
>
> I prefer a target at the very beginning of the month, it is an insurance against
> disaster, and it may allow a quiet August month for the maintainers.
>
> Another issue is the delay between -rc1 and final release.
> The above proposal has only 24 days -rc phase.
> Based on records, we need 30 days for a proper -rc phase.
>
> Taking above requirements into consideration, I propose having a proposal
> deadline earlier by 8 days:
>
> - Proposal deadline: Monday, 8 June 2020
> - Integration deadline: Tuesday, 30 June 2020
> - 20.08-rc1: Friday, 3 July 2020
> - 20.08-rc2: Friday, 17 July 2020
> - 20.08-rc3: Friday, 24 July 2020
> - 20.08-rc4: Friday, 31 July 2020
> - Release: Monday, 3 August 2020
>
>
I think the proposal deadline should be left at Tuesday 16 June, as developers have been working towards this date.
I am ok with the other dates.
Regards,
Bernard.
prev parent reply other threads:[~2020-05-21 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 11:13 Ferruh Yigit
2020-05-14 11:17 ` Ferruh Yigit
2020-05-14 11:49 ` David Marchand
2020-05-15 14:31 ` Kevin Traynor
2020-05-14 13:44 ` Ferruh Yigit
2020-05-15 16:14 ` Thomas Monjalon
2020-05-21 5:47 ` Ajit Khaparde
2020-05-21 8:28 ` Iremonger, Bernard [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:
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=DM6PR11MB2537B3DFF099A1E5FD85E37DEFB70@DM6PR11MB2537.namprd11.prod.outlook.com \
--to=bernard.iremonger@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=arybchenko@solarflare.com \
--cc=asafp@mellanox.com \
--cc=cathal.ohare@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@oss.nxp.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
/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).