[dpdk-dev] DPDK Release Status Meeting 28/3/2019

[dpdk-dev] DPDK Release Status Meeting 28/3/2019

[Ferruh Yigit]

Minutes 28 March 2019
---------------------

Agenda:
* Release Dates
* Subtrees
* Coverity
* Opens


Participants:
* Arm
* Intel
* Marvell
* Mellanox
* NXP
* RedHat


Release Dates
-------------

* v19.05 dates, rc1 date pushed to Wednesday:
  * RC1: *Wednesday, 3 April*
  * Release: Friday, 10 May

* v19.08 dates:
  * Proposal/V1               Monday 03 June   2019  
  * Integration/Merge/RC1     Monday 01 July   2019  
  * Release                   Thurs  01 August 2019

  * schedule update patch:
    https://mails.dpdk.org/archives/web/2019-March/001055.html

* v19.11 dates should be discussed soon


Subtrees
--------

* main
  * More patches to merge
  * Thomas is looking Arm locking patches

* next-net
  * Around 60 patches waiting for review
  * New pmds not merged yet: af_xdp, memif, ifpga ipn3ke, netcope nfb
    * af_xdp updates some other libraries, may go in rc2
    * memif may not make this release

* next-virtio
  * Patches has been merged, tree pulled

* next-crypto
  * ipsec updates mbuf, needs to be addressed
  * ipsec-secgw can be slip to rc2

* next-eventdev
  * no update

* next-pipeline
* next-qos
  * No update, we need attendance from maintainers

* Stable trees
  * 18.08.1-rc3 is waiting for more test
    * 18.08.1 release planned for next Monday
  * 18.11-1-rc2 is out, waiting to be tested
    * Intel & Mellanox test result look good
    * 18.11.1 release planned on 8 April
  * 19.02
    * Short term stable releases discussed on techboard,
      more detail will be on techboard meeting minutes
    * Will be dropped unless there is volunteer
  * 19.11
    * Luca may be tree maintainer


Coverity
--------

* Coverity is back on, John run a new scan with latest code:
  https://scan.coverity.com/projects/dpdk-data-plane-development-kit

* John shared lgtm.com results to the mail list:
  * https://mails.dpdk.org/archives/dev/2019-March/127986.html
  * lgtm dpdk project link:
    https://lgtm.com/projects/g/DPDK/dpdk/alerts/?mode=list


Opens
-----

* Akhil is looking for co-maintainer for crypto sub-tree


DPDK Release Status Meetings
============================

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 an email to "John McNamara <john.mcnamara@intel.com>" for the invite.

[dpdk-dev] DPDK Release Status Meeting 28/3/2019

[Ferruh Yigit]

Minutes 28 March 2019
---------------------

Agenda:
* Release Dates
* Subtrees
* Coverity
* Opens


Participants:
* Arm
* Intel
* Marvell
* Mellanox
* NXP
* RedHat


Release Dates
-------------

* v19.05 dates, rc1 date pushed to Wednesday:
  * RC1: *Wednesday, 3 April*
  * Release: Friday, 10 May

* v19.08 dates:
  * Proposal/V1               Monday 03 June   2019  
  * Integration/Merge/RC1     Monday 01 July   2019  
  * Release                   Thurs  01 August 2019

  * schedule update patch:
    https://mails.dpdk.org/archives/web/2019-March/001055.html

* v19.11 dates should be discussed soon


Subtrees
--------

* main
  * More patches to merge
  * Thomas is looking Arm locking patches

* next-net
  * Around 60 patches waiting for review
  * New pmds not merged yet: af_xdp, memif, ifpga ipn3ke, netcope nfb
    * af_xdp updates some other libraries, may go in rc2
    * memif may not make this release

* next-virtio
  * Patches has been merged, tree pulled

* next-crypto
  * ipsec updates mbuf, needs to be addressed
  * ipsec-secgw can be slip to rc2

* next-eventdev
  * no update

* next-pipeline
* next-qos
  * No update, we need attendance from maintainers

* Stable trees
  * 18.08.1-rc3 is waiting for more test
    * 18.08.1 release planned for next Monday
  * 18.11-1-rc2 is out, waiting to be tested
    * Intel & Mellanox test result look good
    * 18.11.1 release planned on 8 April
  * 19.02
    * Short term stable releases discussed on techboard,
      more detail will be on techboard meeting minutes
    * Will be dropped unless there is volunteer
  * 19.11
    * Luca may be tree maintainer


Coverity
--------

* Coverity is back on, John run a new scan with latest code:
  https://scan.coverity.com/projects/dpdk-data-plane-development-kit

* John shared lgtm.com results to the mail list:
  * https://mails.dpdk.org/archives/dev/2019-March/127986.html
  * lgtm dpdk project link:
    https://lgtm.com/projects/g/DPDK/dpdk/alerts/?mode=list


Opens
-----

* Akhil is looking for co-maintainer for crypto sub-tree


DPDK Release Status Meetings
============================

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 an email to "John McNamara <john.mcnamara@intel.com>" for the invite.

Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019

[David Marchand]

On Thu, Mar 28, 2019 at 1:04 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:

> Coverity
> --------
>
> * Coverity is back on, John run a new scan with latest code:
>   https://scan.coverity.com/projects/dpdk-data-plane-development-kit


The "components" mappings seem quite old/invalid to me:
- we still have the old pmds path à la lib/librte_pmd_XXX
- pmd_bond points to an drivers/net/bond/.
- pmd_mlx4 points to drivers/net/ixgbe/.

And others catches almost everything (400k loc).

John, can you fix it?

-- 
David Marchand

Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019

[David Marchand]

On Thu, Mar 28, 2019 at 1:04 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:

> Coverity
> --------
>
> * Coverity is back on, John run a new scan with latest code:
>   https://scan.coverity.com/projects/dpdk-data-plane-development-kit


The "components" mappings seem quite old/invalid to me:
- we still have the old pmds path à la lib/librte_pmd_XXX
- pmd_bond points to an drivers/net/bond/.
- pmd_mlx4 points to drivers/net/ixgbe/.

And others catches almost everything (400k loc).

John, can you fix it?

-- 
David Marchand

Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019

[Mcnamara, John]

> From: David Marchand [mailto:david.marchand@redhat.com] 
> Sent: Thursday, March 28, 2019 12:48 PM
> To: Yigit, Ferruh <ferruh.yigit@intel.com>; Mcnamara, John <john.mcnamara@intel.com>
> Cc: dpdk-dev <dev@dpdk.org>; Stokes, Ian <ian.stokes@intel.com>; Thomas Monjalon <thomas@monjalon.net>; Jerin Jacob <jerin.jacob@caviumnetworks.com>; Akhil, Goyal <akhil.goyal@nxp.com>; Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Xu, Qian Q <qian.q.xu@intel.com>; Yongseok Koh <yskoh@mellanox.com>; Maxime Coquelin <maxime.coquelin@redhat.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Shahaf Shuler <shahafs@mellanox.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Subject: Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019
> 
> On Thu, Mar 28, 2019 at 1:04 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> Coverity
> --------
> 
> * Coverity is back on, John run a new scan with latest code:
>   https://scan.coverity.com/projects/dpdk-data-plane-development-kit
> 
> The "components" mappings seem quite old/invalid to me:
> - we still have the old pmds path à la lib/librte_pmd_XXX
> - pmd_bond points to an drivers/net/bond/.
> - pmd_mlx4 points to drivers/net/ixgbe/.
> 
> And others catches almost everything (400k loc).
> 
> John, can you fix it?

Yes. Let me know the mappings/changes you want to make and I can implement them or we can make you and admin and you can do it.

John

Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019

[Mcnamara, John]

> From: David Marchand [mailto:david.marchand@redhat.com] 
> Sent: Thursday, March 28, 2019 12:48 PM
> To: Yigit, Ferruh <ferruh.yigit@intel.com>; Mcnamara, John <john.mcnamara@intel.com>
> Cc: dpdk-dev <dev@dpdk.org>; Stokes, Ian <ian.stokes@intel.com>; Thomas Monjalon <thomas@monjalon.net>; Jerin Jacob <jerin.jacob@caviumnetworks.com>; Akhil, Goyal <akhil.goyal@nxp.com>; Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Xu, Qian Q <qian.q.xu@intel.com>; Yongseok Koh <yskoh@mellanox.com>; Maxime Coquelin <maxime.coquelin@redhat.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Shahaf Shuler <shahafs@mellanox.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Subject: Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019
> 
> On Thu, Mar 28, 2019 at 1:04 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> Coverity
> --------
> 
> * Coverity is back on, John run a new scan with latest code:
>   https://scan.coverity.com/projects/dpdk-data-plane-development-kit
> 
> The "components" mappings seem quite old/invalid to me:
> - we still have the old pmds path à la lib/librte_pmd_XXX
> - pmd_bond points to an drivers/net/bond/.
> - pmd_mlx4 points to drivers/net/ixgbe/.
> 
> And others catches almost everything (400k loc).
> 
> John, can you fix it?

Yes. Let me know the mappings/changes you want to make and I can implement them or we can make you and admin and you can do it.

John

Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019

[David Marchand]

On Mon, Apr 1, 2019 at 5:47 PM Mcnamara, John <john.mcnamara@intel.com>
wrote:

> > From: David Marchand [mailto:david.marchand@redhat.com]
> > Sent: Thursday, March 28, 2019 12:48 PM
> > To: Yigit, Ferruh <ferruh.yigit@intel.com>; Mcnamara, John <
> john.mcnamara@intel.com>
> > Cc: dpdk-dev <dev@dpdk.org>; Stokes, Ian <ian.stokes@intel.com>; Thomas
> Monjalon <thomas@monjalon.net>; Jerin Jacob <
> jerin.jacob@caviumnetworks.com>; Akhil, Goyal <akhil.goyal@nxp.com>;
> Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Xu, Qian Q <
> qian.q.xu@intel.com>; Yongseok Koh <yskoh@mellanox.com>; Maxime Coquelin <
> maxime.coquelin@redhat.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Shahaf
> Shuler <shahafs@mellanox.com>; De Lara Guarch, Pablo <
> pablo.de.lara.guarch@intel.com>
> > Subject: Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019
> >
> > On Thu, Mar 28, 2019 at 1:04 PM Ferruh Yigit <ferruh.yigit@intel.com>
> wrote:
> > Coverity
> > --------
> >
> > * Coverity is back on, John run a new scan with latest code:
> >   https://scan.coverity.com/projects/dpdk-data-plane-development-kit
> >
> > The "components" mappings seem quite old/invalid to me:
> > - we still have the old pmds path à la lib/librte_pmd_XXX
> > - pmd_bond points to an drivers/net/bond/.
> > - pmd_mlx4 points to drivers/net/ixgbe/.
> >
> > And others catches almost everything (400k loc).
> >
> > John, can you fix it?
>
> Yes. Let me know the mappings/changes you want to make and I can implement
> them or we can make you and admin and you can do it.
>

I don't particularly care. I could do it, but this would be best effort
anyway.
The question is more: do we want to use coverity on the mid-, long-term ?


-- 
David Marchand

Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019

[David Marchand]

On Mon, Apr 1, 2019 at 5:47 PM Mcnamara, John <john.mcnamara@intel.com>
wrote:

> > From: David Marchand [mailto:david.marchand@redhat.com]
> > Sent: Thursday, March 28, 2019 12:48 PM
> > To: Yigit, Ferruh <ferruh.yigit@intel.com>; Mcnamara, John <
> john.mcnamara@intel.com>
> > Cc: dpdk-dev <dev@dpdk.org>; Stokes, Ian <ian.stokes@intel.com>; Thomas
> Monjalon <thomas@monjalon.net>; Jerin Jacob <
> jerin.jacob@caviumnetworks.com>; Akhil, Goyal <akhil.goyal@nxp.com>;
> Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Xu, Qian Q <
> qian.q.xu@intel.com>; Yongseok Koh <yskoh@mellanox.com>; Maxime Coquelin <
> maxime.coquelin@redhat.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Shahaf
> Shuler <shahafs@mellanox.com>; De Lara Guarch, Pablo <
> pablo.de.lara.guarch@intel.com>
> > Subject: Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019
> >
> > On Thu, Mar 28, 2019 at 1:04 PM Ferruh Yigit <ferruh.yigit@intel.com>
> wrote:
> > Coverity
> > --------
> >
> > * Coverity is back on, John run a new scan with latest code:
> >   https://scan.coverity.com/projects/dpdk-data-plane-development-kit
> >
> > The "components" mappings seem quite old/invalid to me:
> > - we still have the old pmds path à la lib/librte_pmd_XXX
> > - pmd_bond points to an drivers/net/bond/.
> > - pmd_mlx4 points to drivers/net/ixgbe/.
> >
> > And others catches almost everything (400k loc).
> >
> > John, can you fix it?
>
> Yes. Let me know the mappings/changes you want to make and I can implement
> them or we can make you and admin and you can do it.
>

I don't particularly care. I could do it, but this would be best effort
anyway.
The question is more: do we want to use coverity on the mid-, long-term ?


-- 
David Marchand

Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019

[Bruce Richardson]

On Mon, Apr 01, 2019 at 09:10:02PM +0200, David Marchand wrote:
> On Mon, Apr 1, 2019 at 5:47 PM Mcnamara, John <john.mcnamara@intel.com>
> wrote:
> 
> > > From: David Marchand [mailto:david.marchand@redhat.com]
> > > Sent: Thursday, March 28, 2019 12:48 PM
> > > To: Yigit, Ferruh <ferruh.yigit@intel.com>; Mcnamara, John <
> > john.mcnamara@intel.com>
> > > Cc: dpdk-dev <dev@dpdk.org>; Stokes, Ian <ian.stokes@intel.com>; Thomas
> > Monjalon <thomas@monjalon.net>; Jerin Jacob <
> > jerin.jacob@caviumnetworks.com>; Akhil, Goyal <akhil.goyal@nxp.com>;
> > Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Xu, Qian Q <
> > qian.q.xu@intel.com>; Yongseok Koh <yskoh@mellanox.com>; Maxime Coquelin <
> > maxime.coquelin@redhat.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Shahaf
> > Shuler <shahafs@mellanox.com>; De Lara Guarch, Pablo <
> > pablo.de.lara.guarch@intel.com>
> > > Subject: Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019
> > >
> > > On Thu, Mar 28, 2019 at 1:04 PM Ferruh Yigit <ferruh.yigit@intel.com>
> > wrote:
> > > Coverity
> > > --------
> > >
> > > * Coverity is back on, John run a new scan with latest code:
> > >   https://scan.coverity.com/projects/dpdk-data-plane-development-kit
> > >
> > > The "components" mappings seem quite old/invalid to me:
> > > - we still have the old pmds path à la lib/librte_pmd_XXX
> > > - pmd_bond points to an drivers/net/bond/.
> > > - pmd_mlx4 points to drivers/net/ixgbe/.
> > >
> > > And others catches almost everything (400k loc).
> > >
> > > John, can you fix it?
> >
> > Yes. Let me know the mappings/changes you want to make and I can implement
> > them or we can make you and admin and you can do it.
> >
> 
> I don't particularly care. I could do it, but this would be best effort
> anyway.
> The question is more: do we want to use coverity on the mid-, long-term ?
>
I think it's worth continuing to use. It's been useful over the years we've
been using it thus far.

/Bruce

Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019

[Bruce Richardson]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 1955 bytes --]

On Mon, Apr 01, 2019 at 09:10:02PM +0200, David Marchand wrote:
> On Mon, Apr 1, 2019 at 5:47 PM Mcnamara, John <john.mcnamara@intel.com>
> wrote:
> 
> > > From: David Marchand [mailto:david.marchand@redhat.com]
> > > Sent: Thursday, March 28, 2019 12:48 PM
> > > To: Yigit, Ferruh <ferruh.yigit@intel.com>; Mcnamara, John <
> > john.mcnamara@intel.com>
> > > Cc: dpdk-dev <dev@dpdk.org>; Stokes, Ian <ian.stokes@intel.com>; Thomas
> > Monjalon <thomas@monjalon.net>; Jerin Jacob <
> > jerin.jacob@caviumnetworks.com>; Akhil, Goyal <akhil.goyal@nxp.com>;
> > Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Xu, Qian Q <
> > qian.q.xu@intel.com>; Yongseok Koh <yskoh@mellanox.com>; Maxime Coquelin <
> > maxime.coquelin@redhat.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Shahaf
> > Shuler <shahafs@mellanox.com>; De Lara Guarch, Pablo <
> > pablo.de.lara.guarch@intel.com>
> > > Subject: Re: [dpdk-dev] DPDK Release Status Meeting 28/3/2019
> > >
> > > On Thu, Mar 28, 2019 at 1:04 PM Ferruh Yigit <ferruh.yigit@intel.com>
> > wrote:
> > > Coverity
> > > --------
> > >
> > > * Coverity is back on, John run a new scan with latest code:
> > >   https://scan.coverity.com/projects/dpdk-data-plane-development-kit
> > >
> > > The "components" mappings seem quite old/invalid to me:
> > > - we still have the old pmds path à la lib/librte_pmd_XXX
> > > - pmd_bond points to an drivers/net/bond/.
> > > - pmd_mlx4 points to drivers/net/ixgbe/.
> > >
> > > And others catches almost everything (400k loc).
> > >
> > > John, can you fix it?
> >
> > Yes. Let me know the mappings/changes you want to make and I can implement
> > them or we can make you and admin and you can do it.
> >
> 
> I don't particularly care. I could do it, but this would be best effort
> anyway.
> The question is more: do we want to use coverity on the mid-, long-term ?
>
I think it's worth continuing to use. It's been useful over the years we've
been using it thus far.

/Bruce