From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK Release Status Meeting 31/05/2018
Date: Thu, 31 May 2018 17:18:13 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F35A8E6@IRSMSX103.ger.corp.intel.com> (raw)
Minutes from the weekly DPDK Release Status Meeting.
The DPDK Release Status Meeting is intended for DPDK Committers to discuss
the status of the master tree and sub-trees, and for project managers to
track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just
send me and email and I will send you the invite.
Minutes 31 May 2018
Agenda:
* DPDK 18.05 release.
* Retrospective on 18.05.
* Testing of stable releases.
Participants:
* Intel
* Cavium
* Mellanox
* NXP
* 6Wind
* RedHat
DPDK 18.05 release.
* DPDK 18.08 "The Venky Release" is out. \o/
* Thanks to all the maintainers and contributors.
* See the release notes for the full stats:
http://dpdk.org/ml/archives/announce/2018-May/000204.html
Retrospective on 18.05.
* What went well.
* Largest DPDK release ever.
* Lots of contributors from all the main companies involved in networking.
* Collaboration on major features between companies in the community.
* What didn't go so well.
* The release was very late and required a lot of release candidates.
* RC1 was late and low quality.
* Many major defects found in RC testing.
* Some reviews were slow or late.
* What can we do differently next time.
* Should we change the number of releases per year from 4 to 3 or 2?
* Merge earlier from subtrees: every 7-10 days.
* Push patches earlier.
* Review patches more critically. Does every feature/patch need to go in.
* Use unit tests more
* Make them a requirement for any sizeable code.
* Make them easier to write/use/run.
* Add a make/meson target for generating coverage results from units
tests. Any volunteers?
* Hold more strictly to the release milestone dates.
Testing of stable releases.
* Luca Boccassi asked about testing of the stable release.
* All major contributing companies should confirm test results on the stable
releases.
* Luca will send an email to the list about it:
http://dpdk.org/ml/archives/dev/2018-May/103249.html
next reply other threads:[~2018-05-31 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 17:18 Mcnamara, John [this message]
2018-05-31 18:40 ` Wiles, Keith
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=B27915DBBA3421428155699D51E4CFE23F35A8E6@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.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).