From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: dev@dpdk.org, techboard@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes of June 6
Date: Tue, 19 Jun 2018 10:06:37 +0530 [thread overview]
Message-ID: <20180619043629.GA3053@jerin> (raw)
Meeting notes for the DPDK technical board meeting held on 2018-06-06
Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Olivier Matz
- Thomas Monjalon
0) The Review Process - Timelines
a) A patch without any comments for 3 weeks shall be considered for apply to
subtree or main tree by the respective tree maintainer.
b) Once a patch has been acked by the relevant maintainer, reviewers may still
comment on it for a further two weeks.
After that time, the patch should be merged into the relevant git tree for the next release.
It is documented at http://dpdk.org/doc/guides/contributing/patches.html#steps-to-getting-your-patch-merged
c) Thomas will try to pull the changes from every subtree weekly.
The planned day is Thursday/Friday.
Sub tree maintainer can choose private pull request or specific branch scheme to share
the tree based on subtree maintainer and Thomas's preference.
1) New dpdk website by the Linux Foundation
a) Linux Foundation is working on a new dpdk website and its URL is
https://dpdk.lfprojects.linuxfoundation.org/
b) Encourage everyone to review and provide feedback and/or report
missing links such as (mailman, cgit, git, patchwork, bugzilla, doc, etc)
3) Next meeting will be on June 20 and Konstantin will chair it
next reply other threads:[~2018-06-19 4:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 4:36 Jerin Jacob [this message]
[not found] <VI1PR0401MB2541F07E6E640ED569918E6089E40@VI1PR0401MB2541.eurprd04.prod.outlook.com>
2019-06-20 8:33 ` [dpdk-dev] DPDK Techboard " Hemant Agrawal
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=20180619043629.GA3053@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=techboard@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).