From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] community collaboration
Date: Mon, 20 Oct 2014 23:42:52 +0200 [thread overview]
Message-ID: <1739627.QC0qiqQoyT@xps13> (raw)
Hello readers,
We are currently targetting a new release (1.8.0) in few weeks.
It would be good to have most of the important pending patches in.
But writing and sending code is only the first part. After come the reviews.
Before integration, we need to validate the design of the new features,
check if improvements are really good, be sure that the code is enough
commented, maintainable and that there is not (a lot of) typos.
In short you can help by making reviews.
Anyone is welcome, please consider that reviews are part of the developper job.
Please, do not review only patches from your company. I'd prefer cross reviews.
I have noticed too many loose reviews when people are from the same one.
Thank you very much
--
Thomas
reply other threads:[~2014-10-20 21:34 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=1739627.QC0qiqQoyT@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).