From: Andrew Rybchenko <arybchenko@solarflare.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Proposed adjustment to the 17.05 V1 date
Date: Mon, 20 Feb 2017 17:22:02 +0300 [thread overview]
Message-ID: <08409ae5-fbdb-9766-7e61-809cd9b69502@solarflare.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2026D223F@IRSMSX103.ger.corp.intel.com>
On 02/20/2017 03:15 PM, Mcnamara, John wrote:
> Hi
>
> Due to a very short window between the 17.02 release and the V1 deadline we would like to propose increasing the V1 deadline by 5 days, without increasing the Merge and Release dates.
>
> The current public schedule is:
>
> 17.05 Schedule (Current)
> Proposal deadline: February 26
> Integration deadline: March 30
> Release: May 2
>
> The new proposed schedule is:
>
> 17.05 Schedule (Proposed)
> Proposal deadline: March 3
> Integration deadline: March 30
> Release: May 2
+1, it would be really good
next prev parent reply other threads:[~2017-02-20 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 12:15 Mcnamara, John
2017-02-20 13:37 ` Jerin Jacob
2017-02-20 14:22 ` Andrew Rybchenko [this message]
2017-02-21 1:11 ` Yuanhan Liu
2017-02-21 9:12 ` 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=08409ae5-fbdb-9766-7e61-809cd9b69502@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.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).