From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Subject: releases scheduling
Date: Thu, 12 May 2016 11:38:54 +0200 [thread overview]
Message-ID: <6696452.ekNDdmaYZx@xps13> (raw)
Hi everybody,
The deadlines for the next releases are available on the website:
http://dpdk.org/dev/roadmap#dates
Release 16.07
Proposal deadline: May 8
Integration deadline: June 16
Release: July 18
Release 16.11
Proposal deadline: August 28
Integration deadline: September 30
Release: November 2
Release 17.02
Release: February 1
Release 17.05
Release: May 2
Release 17.08
Release: August 1
Release 17.11
Release: November 2
The planning try to preserve some of the major holiday periods
(February, May, August, December).
Let's put more details for the next year:
Release 17.02
Proposal deadline: December 4
Integration deadline: January 5
Release: February 1
Release 17.05
Proposal deadline: February 26
Integration deadline: March 30
Release: May 2
Release 17.08
Proposal deadline: May 28
Integration deadline: June 29
Release: August 1
As usual, comments are welcome
next reply other threads:[~2016-05-12 9:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 9:38 Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-13 19:22 releases scheduling Thomas Monjalon
2015-12-15 13:37 ` O'Driscoll, Tim
2015-12-15 14:24 ` Arnon Warshavsky
2015-12-15 14:42 ` Wiles, Keith
2015-12-15 15:39 ` Jay Rolette
2015-12-15 19:15 ` Dave Neary
2015-12-15 21:15 ` Wiles, Keith
2015-12-15 21:40 ` Vincent JARDIN
2015-12-19 0:01 ` Thomas Monjalon
2015-12-19 2:16 ` Wiles, Keith
2015-12-19 9:47 ` Thomas Monjalon
2015-12-19 16:21 ` Wiles, Keith
2015-12-19 20:13 ` Thomas Monjalon
2015-12-19 22:58 ` O'Driscoll, Tim
2015-12-27 20:04 ` 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=6696452.ekNDdmaYZx@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
/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.