DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] releases scheduling
Date: Sun, 13 Dec 2015 20:22:59 +0100	[thread overview]
Message-ID: <1667533.heuKAiE6KB@xps13> (raw)

Hi all,

We need to define the deadlines for the next releases.
During 2015, we were doing a release every 4 months.
If we keep the same pace, the next releases would be:
	2.3: end of March
	2.4: end of July
	2.5: end of November

However, things move fast and it may be a bit long to wait 4 months for
a feature. That's why I suggest to progressively shorten release terms:
	2.3: end of March
	2.4: mid July
	2.5: end of October
and continue with a release every 3 months:
	2.6: end of January
	2.7: end of April
	2.8: end of July
This planning would preserve some of the major holiday periods
(February, May, August, December).

The first period, for the first submission of a feature, was 2 months long.
Then we had 2 other months to discuss, merge and fix.
We should shorten only the first period.

Anyway, the next deadlines should be unchanged:
	- January 31: end of first submission phase
	- March 31: release 2.3

Opinions are welcome.

             reply	other threads:[~2015-12-13 19:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-13 19:22 Thomas Monjalon [this message]
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
2016-05-12  9:38 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=1667533.heuKAiE6KB@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 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).