[dpdk-dev] DPDK Release Status Meeting 24/05/2018

["Mcnamara, John" <john.mcnamara@intel.com>]

The DPDK Release Status Meeting is mainly intended for DPDK Committers to
discuss the status of the master and sub-trees. It is also intended as an
update for project managers who need 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. I will forward the minutes on a
weekly basis.

Minutes 24 May 2018

Agenda
    * RC5 Status
    * RC6 and Release
    * Other items

Participants:
    * Intel
    * Cavium
    * Mellanox
    * NXP
    * 6Wind
    * RedHat

RC5 Status

    * Testing
        * Intel Testing
            * No major issues
            * No build issues
        * NXP
            * Good
        * Cavium
            * 1 issue found in bonding testing - patch submitted

    * RC5 Main Issues
        * Note, the following 2 issues will be included in the release. The
          will be marked as known issues in the release notes.
        * Bugzilla #50 - Secondary process launch is
          unreliable.
          https://dpdk.org/tracker/show_bug.cgi?id=50
          Secondary process initialization was known to be unreliable before,
          with numerous workarounds already being available and
          documented. However, DPDK version 18.05 has introduced memory
          subsystem rework, which has made situation worse due to much more
          memory being pre-reserved at initialization.
        * Bugzilla #48 -Unexpected performance regression since CVE-2018-1059
          fix with vector path.
          https://dpdk.org/tracker/show_bug.cgi?id=48
          A small performance drop was expected with CVE-2018-1059 fix
          integration.  While this expectation is verified for mast cases
          (less than 3% drop), a bigger drop is seen when using vector path in
          guest with small packets.

RC6+
  * Only critical fixes into RC6
  * Docs also. Send deprecation notices.
  * Planned for Friday 25 May. End of day.
  * Automated test will run over weekend.
  * Results will be evaluated on Monday 28th May.
  * Depending on the results the release will be Monday or Tuesday 28th
    or 29th May.
  * All major contributors should evaluate on Monday and inform Thomas
    of your results: Intel, Cavium, Mellanox, NXP, 6Wind, RedHat,
    Debian, Canonical, etc.
  * Note: can all major contributors submit a "Tested Platforms" section
    to the release notes. Like this:
    http://dpdk.org/doc/guides/rel_notes/release_17_11.html#tested-platforms


Other
  * We will conduct a retrospective of 18.05 at next weeks
    meeting. Please think about:
      * What went well
      * What went badly
      * What we can do to improve