From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Proposed adjustment to the 17.05 V1 date
Date: Mon, 20 Feb 2017 19:07:40 +0530 [thread overview]
Message-ID: <20170220133739.GA11054@localhost.localdomain> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2026D223F@IRSMSX103.ger.corp.intel.com>
On Mon, Feb 20, 2017 at 12:15:26PM +0000, 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
> Regards,
>
> John
next prev parent reply other threads:[~2017-02-20 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 12:15 Proposed adjustment to the 17.05 V1 date Mcnamara, John
2017-02-20 13:37 ` Jerin Jacob [this message]
2017-02-20 14:22 ` Andrew Rybchenko
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=20170220133739.GA11054@localhost.localdomain \
--to=jerin.jacob@caviumnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.