DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, John McNamara <john.mcnamara@intel.com>,
	"Stokes, Ian" <ian.stokes@intel.com>,
	Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	"Akhil, Goyal" <akhil.goyal@nxp.com>,
	Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
	Qian Xu <qian.q.xu@intel.com>, Yongseok Koh <yskoh@mellanox.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 21/2/2019
Date: Thu, 21 Feb 2019 17:19:00 +0100	[thread overview]
Message-ID: <2698155.nIaUjHGsBl@xps> (raw)
In-Reply-To: <83259c98-9d32-02d8-fe09-d67839658eca@intel.com>

21/02/2019 17:09, Ferruh Yigit:
> * v19.08 proposal, please comment:
>   * Proposal/V1               Friday 07 June   2019  
>   * Integration/Merge/RC1     Friday 05 July   2019  
>   * Release                   Thurs  01 August 2019 

Fixes usually take longer during July, so we may be short of time.
Could we plan a bit more time between -rc1 and release?

A proposal:
	* Proposal/V1             Monday 03 June
	* Integration/Merge/RC1   Monday 01 July
	* Release                 Thurs  01 August

  reply	other threads:[~2019-02-21 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 16:09 Ferruh Yigit
2019-02-21 16:19 ` Thomas Monjalon [this message]
2019-02-21 17:43 ` Luca Boccassi
2019-02-21 18:16   ` Thomas Monjalon
2019-03-06 15:27   ` Luca Boccassi
2019-03-06 15:45     ` Richardson, Bruce

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=2698155.nIaUjHGsBl@xps \
    --to=thomas@monjalon.net \
    --cc=akhil.goyal@nxp.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=ian.stokes@intel.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=john.mcnamara@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=shahafs@mellanox.com \
    --cc=yskoh@mellanox.com \
    /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).