From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-announce] features review and integration for 18.02
Date: Fri, 01 Dec 2017 15:44:43 +0100 [thread overview]
Message-ID: <2816945.GYy50u2GaR@xps> (raw)
Reminder of the planning for the release 18.02:
- Proposal deadline: November 30, 2017
- Integration deadline: January 10, 2018
- Release: February 5, 2018
The proposal period is now over.
It is time to focus on proposals which were done.
It means everybody should review details and comment the ideas,
before they are integrated for 18.02.
In order to help your patches being reviewed, you should make sure
that the maintainers of the code are the recipients of the patches.
Otherwise you can add them while asking for comments.
Note:
You can use the file MAINTAINERS or the tool devtools/get-maintainer.sh.
Then the maintainers of the code are responsible to make sure the patches
are well reviewed. Everybody can help giving some comments.
At the end, the git tree maintainers (also called committers) will be
responsible to integrate the patches on time.
More details on the process:
http://dpdk.org/doc/guides/contributing/patches.html#the-review-process
Do not hesitate to ping when progress is too slow,
and to help making progress on reviewing your peers.
Collaboration is the key to succeed.
Thank you
reply other threads:[~2017-12-01 14:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2816945.GYy50u2GaR@xps \
--to=thomas@monjalon.net \
--cc=announce@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).