From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] deadlines postponed
Date: Thu, 22 Feb 2018 10:55:06 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB97725890575764@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAA4AD1D13@IRSMSX108.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of O'Driscoll, Tim
> Sent: Thursday, February 22, 2018 10:44 AM
> To: Thomas Monjalon <thomas@monjalon.net>; dev@dpdk.org
> Subject: Re: [dpdk-dev] deadlines postponed
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> > Sent: Thursday, February 22, 2018 10:34 AM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] deadlines postponed
> >
> > Hi,
> >
> > I propose to shift the proposal deadline and the integration deadline
> > for 18.05:
> > - Proposal deadline: March 9, 2018
> > - Integration deadline: April 6, 2018
> > - Release: May 4, 2018
> >
> > The idea is to follow these guidelines:
> > - more time before the proposal deadline
> > - 4 weeks for integration in RC1
> > - 4 weeks for bugs fixing after RC1
> >
> > You can look at this web patch for more details:
> > http://dpdk.org/ml/archives/web/2018-February/000580.html
> >
> > Opinions?
>
> +1
>
> At the moment, the proposal deadline is very soon after the previous release. Moving this out a little would allow extra time for
> development, and would still keep reasonable intervals for integration and testing/bug fixing.
+1 from me too.
next prev parent reply other threads:[~2018-02-22 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 10:33 Thomas Monjalon
2018-02-22 10:44 ` O'Driscoll, Tim
2018-02-22 10:55 ` Ananyev, Konstantin [this message]
2018-02-22 13:22 ` Gaëtan Rivet
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=2601191342CEEE43887BDE71AB97725890575764@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
--cc=tim.odriscoll@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).