[dpdk-dev] DPDK Release Status Meeting 16/04/2020

[dpdk-dev] DPDK Release Status Meeting 16/04/2020

[Ferruh Yigit]

Minutes 16 April 2020
---------------------

Agenda:
* Release Dates
* Subtrees
* OvS

Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat


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

* v20.05 dates:
  * Integration/Merge/RC1 pushed to	*Thursday 23 April 2020*
  * Release:				Wednesday 20 May 2020

  * Marvell, Arm, Mellanox & Broadcom already sent roadmap for 20.05, all
    vendors please share the roadmap for the release.


Subtrees
--------

* main
    * There are still lots of patches, a lot of reviews are missing
    * Sub-trees will be pulled next week Monday/Tuesday
      * Sub-trees should be ready by EOD Friday or Saturday
    * Thomas did review on graph library, planning to get it as it is
    * Trace library will be merged for -rc1, the review was missing but at least
      feedback requested
    * Some library features may go in for -rc2 due to big backlog
    * If the work is not finished, planning to block related patches
      * Example: ABI breaks for false positive, don't get patches that
                 breaks ABI before fixing the ABI check tools.

* next-net
  * Less than 50 patches in the backlog
  * Some ethdev patches are not merged yet, close but not ready for -rc1
  * mlx set that break the ABI not clarified yet, it may be dropped from tree

* next-crypto
  * ~50 patches in backlog, reviewed most of them, will apply today
  * ipsec patch depends on hash change which is for main repo
    * Thomas will look to it with priority
  * ABI related crypto patch will be reviewed today
  * There is a reported build error from Raslan

* next-eventdev
  * No more patches for -rc1, already pulled to main

* next-virtio
  * Lots of reviews done last and this week, still have bunch of patches
  * Some reviewed already and can be merged quickly
  * Ones waiting for new version can go into next -rc
  * There is a performance optimization for Arm patch waiting for review
    * one way barrier for split vring idx

* next-net-intel
  * Waiting for some major patchsets related to iavf
  * They may not be ready for tomorrow

* next-net-mlx
  * There are some big patchsets waiting, they are not blocking the -rc1
  * flow aging patches waiting to be merged in next-net

* next-net-mrvl
  * All patches merged for -rc1

* next-net-brcm
  * There is a big patch merged recently, will pull it to next-net today

* LTS

  * 18.11.7 released
    * http://inbox.dpdk.org/dev/20200415173701.19706-1-ktraynor@redhat.com/


OvS
---

* There was another meeting last week, ping Kevin for details.



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 16/04/2020

[Thomas Monjalon]

16/04/2020 12:06, Ferruh Yigit:
>   * Marvell, Arm, Mellanox & Broadcom already sent roadmap for 20.05, all
>     vendors please share the roadmap for the release.

I think it is too late now for 20.05 roadmap :-)

> Subtrees
> --------
> 
> * main
>     * There are still lots of patches, a lot of reviews are missing
>     * Sub-trees will be pulled next week Monday/Tuesday
>       * Sub-trees should be ready by EOD Friday or Saturday
>     * Thomas did review on graph library, planning to get it as it is

No I did not review rte_graph.
But as it is here for long, it should be merged.

>     * Trace library will be merged for -rc1, the review was missing but at least
>       feedback requested

David worked on rte_trace reviews.
More reviews were expected.
We hope there will be more feedback after the merge as experimental.
Please let's have open feedback, don't be shy asking for rework
if you have any enhancement idea.

>     * Some library features may go in for -rc2 due to big backlog

We will try to minimize feature additions in -rc2 if any.

>     * If the work is not finished, planning to block related patches
>       * Example: ABI breaks for false positive, don't get patches that
>                  breaks ABI before fixing the ABI check tools.

Yes we should block patches more often to get work done.
We can find other examples in crypto or ethdev.
We need to define clear deadlines.
Example: any patch in a PMD will be blocked after a deadline
if the PMD does not comply with the requested rework,
as RTE_ETH_DEV_CLOSE_REMOVE behaviour.

> * next-net
>   * Less than 50 patches in the backlog
>   * Some ethdev patches are not merged yet, close but not ready for -rc1
>   * mlx set that break the ABI not clarified yet, it may be dropped from tree
> 
> * next-crypto
>   * ~50 patches in backlog, reviewed most of them, will apply today
>   * ipsec patch depends on hash change which is for main repo
>     * Thomas will look to it with priority

It seems hash patches are not ready or not reviewed.

>   * ABI related crypto patch will be reviewed today
>   * There is a reported build error from Raslan

Looks to be not reproduced.

[...]
>   * 18.11.7 released
>     * http://inbox.dpdk.org/dev/20200415173701.19706-1-ktraynor@redhat.com/

Congratulations Kevin!

Re: [dpdk-dev] DPDK Release Status Meeting 16/04/2020

[Ferruh Yigit]

On 4/16/2020 11:49 AM, Thomas Monjalon wrote:
> 16/04/2020 12:06, Ferruh Yigit:
>>   * Marvell, Arm, Mellanox & Broadcom already sent roadmap for 20.05, all
>>     vendors please share the roadmap for the release.
> 
> I think it is too late now for 20.05 roadmap :-)
> 
>> Subtrees
>> --------
>>
>> * main
>>     * There are still lots of patches, a lot of reviews are missing
>>     * Sub-trees will be pulled next week Monday/Tuesday
>>       * Sub-trees should be ready by EOD Friday or Saturday
>>     * Thomas did review on graph library, planning to get it as it is
> 
> No I did not review rte_graph.
> But as it is here for long, it should be merged.
> 
>>     * Trace library will be merged for -rc1, the review was missing but at least
>>       feedback requested
> 
> David worked on rte_trace reviews.
> More reviews were expected.
> We hope there will be more feedback after the merge as experimental.
> Please let's have open feedback, don't be shy asking for rework
> if you have any enhancement idea.
> 
>>     * Some library features may go in for -rc2 due to big backlog
> 
> We will try to minimize feature additions in -rc2 if any.
> 
>>     * If the work is not finished, planning to block related patches
>>       * Example: ABI breaks for false positive, don't get patches that
>>                  breaks ABI before fixing the ABI check tools.
> 
> Yes we should block patches more often to get work done.
> We can find other examples in crypto or ethdev.
> We need to define clear deadlines.
> Example: any patch in a PMD will be blocked after a deadline
> if the PMD does not comply with the requested rework,
> as RTE_ETH_DEV_CLOSE_REMOVE behaviour.
> 
>> * next-net
>>   * Less than 50 patches in the backlog
>>   * Some ethdev patches are not merged yet, close but not ready for -rc1
>>   * mlx set that break the ABI not clarified yet, it may be dropped from tree
>>
>> * next-crypto
>>   * ~50 patches in backlog, reviewed most of them, will apply today
>>   * ipsec patch depends on hash change which is for main repo
>>     * Thomas will look to it with priority
> 
> It seems hash patches are not ready or not reviewed.
> 
>>   * ABI related crypto patch will be reviewed today
>>   * There is a reported build error from Raslan
> 
> Looks to be not reproduced.

I think this may be valid issue, but reproduced randomly, because in make build,
the ipsec dependency to hash library looks missing.

> 
> [...]
>>   * 18.11.7 released
>>     * http://inbox.dpdk.org/dev/20200415173701.19706-1-ktraynor@redhat.com/
> 
> Congratulations Kevin!
> 
> 
>