[dpdk-dev] [dpdk-announce] release candidate 20.05-rc4

[dpdk-dev] [dpdk-announce] release candidate 20.05-rc4

[Thomas Monjalon]

A new DPDK release candidate is ready for testing:
	https://git.dpdk.org/dpdk/tag/?id=v20.05-rc4

There are 44 new patches in this snapshot.

Release notes:
	http://doc.dpdk.org/guides/rel_notes/release_20_05.html
Some deprecation notices might be added if reviewed on time.

This is the last release candidate for DPDK 20.05.
After -rc4 there should be only doc updates.
Please share some release validation results
by replying to this message (at dev@dpdk.org).
If no critical issue is reported, 20.05 will be closed on Tuesday 26 May.

If you are preparing the next release cycle, please send your v1 patches
before the 20.08 proposal deadline, the Friday 12 June.
It is also time to build an estimated roadmap for the next cycles.

Thank you everyone

Re: [dpdk-dev] [dpdk-announce] release candidate 20.05-rc4

[Thinh Tran]

Hi-

IBM - DPDK on Power result

*Basic PF on Mallanox: No new errors or regressions were seen.
*Performance: no degradation compared to 20.02

System tested:
  - IBM Power9 Model 8335-101 CPU: 2.3 (pvr 004e 1203)
Tested NICs:
  - Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
  - firmware version: 16.26.4012
  - MLNX_OFED_LINUX-4.7-3.2.9.1


Regards,
Thinh Tran

On 5/24/2020 7:09 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> 	https://git.dpdk.org/dpdk/tag/?id=v20.05-rc4
> 
> There are 44 new patches in this snapshot.
> 
> Release notes:
> 	http://doc.dpdk.org/guides/rel_notes/release_20_05.html
> Some deprecation notices might be added if reviewed on time.
> 
> This is the last release candidate for DPDK 20.05.
> After -rc4 there should be only doc updates.
> Please share some release validation results
> by replying to this message (at dev@dpdk.org).
> If no critical issue is reported, 20.05 will be closed on Tuesday 26 May.
> 
> If you are preparing the next release cycle, please send your v1 patches
> before the 20.08 proposal deadline, the Friday 12 June.
> It is also time to build an estimated roadmap for the next cycles.
> 
> Thank you everyone
> 
>