* [dpdk-dev] DPDK Release Status Meeting 25/4/2019
@ 2019-04-25 13:15 Ferruh Yigit
2019-04-25 13:15 ` Ferruh Yigit
0 siblings, 1 reply; 2+ messages in thread
From: Ferruh Yigit @ 2019-04-25 13:15 UTC (permalink / raw)
To: dpdk-dev
Cc: John McNamara, Stokes, Ian, Thomas Monjalon, Jerin Jacob, Akhil,
Goyal, Cristian Dumitrescu, Qian Xu, Yongseok Koh,
Maxime Coquelin, Qi Zhang, Shahaf Shuler, Pablo de Lara
Minutes 25 April 2019
---------------------
Agenda:
* Release Dates
* RC2 status
* Subtrees
* OvS
* Opens
Participants:
* Debian
* Intel
* Marvell
* Mellanox
* NXP
* RedHat
Release Dates
-------------
* v19.05 dates, RC3 date pushed to Thursday, 2 May:
* RC2 is released on Monday, 22 April
* RC3: *Thursday, 2 May*
* RC4: Wednesday, 8 May
* Release: Friday, 10 May
* May 1-4 inclusive is holiday in PRC, Intel testing won't be
available during that time
* v19.08 dates:
* Proposal/V1 Monday 03 June 2019
* Integration/Merge/RC1 Monday 01 July 2019
* Release Thurs 01 August 2019
* Schedule updated on roadmap page:
https://core.dpdk.org/roadmap/
* v19.11 proposed dates, *please comment*,
* Proposal/V1 Friday 06 September 2019
* Integration/Merge/RC1 Friday 11 October 2019
* Release Friday 08 November 2019
* Constrains:
* PRC holidays on October 1-7 inclusive, rc1 shouldn't overlap with it
* US DPDK Summit on mid November, better to have release before summit
RC2 status
----------
* RC2 Intel test results looks good, no major issue detected
Subtrees
--------
* main
* RCU library will be merged after validated by NXP, Marvell & Intel
* next-net
* A few fixes, no major issue
* next-virtio
* No patches for rc3
* next-crypto
* Akhil get some fix + doc patches today/tomorrow
* ipsec-secgw sample app patches won't able to make the release
* next-eventdev
* No patches for rc3
* next-pipeline
* next-qos
* No update, we need attendance from maintainer
* Stable trees
* 18.11.2 is in progress, ~120 fixes merged
OvS
---
* OvS master/2.11.x release moved to 18.11.1
* For DPDK 17.11, OvS is testing 17.11.6-rc1
* For OvS testing on DPDK Community Lab, there is a discussion about having
a test branch
Opens
-----
* Akhil is looking for co-maintainer for crypto sub-tree
* Static analysis:
* There are new defects with rc2, but overall number of defects are reducing
* John is looking for a way to automate lgtm.com findings
* A patch to fix all document spelling errors has been sent by John,
there will be new version of it before release
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [dpdk-dev] DPDK Release Status Meeting 25/4/2019
2019-04-25 13:15 [dpdk-dev] DPDK Release Status Meeting 25/4/2019 Ferruh Yigit
@ 2019-04-25 13:15 ` Ferruh Yigit
0 siblings, 0 replies; 2+ messages in thread
From: Ferruh Yigit @ 2019-04-25 13:15 UTC (permalink / raw)
To: dpdk-dev
Cc: John McNamara, Stokes, Ian, Thomas Monjalon, Jerin Jacob, Akhil,
Goyal, Cristian Dumitrescu, Qian Xu, Yongseok Koh,
Maxime Coquelin, Qi Zhang, Shahaf Shuler, Pablo de Lara
Minutes 25 April 2019
---------------------
Agenda:
* Release Dates
* RC2 status
* Subtrees
* OvS
* Opens
Participants:
* Debian
* Intel
* Marvell
* Mellanox
* NXP
* RedHat
Release Dates
-------------
* v19.05 dates, RC3 date pushed to Thursday, 2 May:
* RC2 is released on Monday, 22 April
* RC3: *Thursday, 2 May*
* RC4: Wednesday, 8 May
* Release: Friday, 10 May
* May 1-4 inclusive is holiday in PRC, Intel testing won't be
available during that time
* v19.08 dates:
* Proposal/V1 Monday 03 June 2019
* Integration/Merge/RC1 Monday 01 July 2019
* Release Thurs 01 August 2019
* Schedule updated on roadmap page:
https://core.dpdk.org/roadmap/
* v19.11 proposed dates, *please comment*,
* Proposal/V1 Friday 06 September 2019
* Integration/Merge/RC1 Friday 11 October 2019
* Release Friday 08 November 2019
* Constrains:
* PRC holidays on October 1-7 inclusive, rc1 shouldn't overlap with it
* US DPDK Summit on mid November, better to have release before summit
RC2 status
----------
* RC2 Intel test results looks good, no major issue detected
Subtrees
--------
* main
* RCU library will be merged after validated by NXP, Marvell & Intel
* next-net
* A few fixes, no major issue
* next-virtio
* No patches for rc3
* next-crypto
* Akhil get some fix + doc patches today/tomorrow
* ipsec-secgw sample app patches won't able to make the release
* next-eventdev
* No patches for rc3
* next-pipeline
* next-qos
* No update, we need attendance from maintainer
* Stable trees
* 18.11.2 is in progress, ~120 fixes merged
OvS
---
* OvS master/2.11.x release moved to 18.11.1
* For DPDK 17.11, OvS is testing 17.11.6-rc1
* For OvS testing on DPDK Community Lab, there is a discussion about having
a test branch
Opens
-----
* Akhil is looking for co-maintainer for crypto sub-tree
* Static analysis:
* There are new defects with rc2, but overall number of defects are reducing
* John is looking for a way to automate lgtm.com findings
* A patch to fix all document spelling errors has been sent by John,
there will be new version of it before release
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-04-25 13:15 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-04-25 13:15 [dpdk-dev] DPDK Release Status Meeting 25/4/2019 Ferruh Yigit
2019-04-25 13:15 ` Ferruh Yigit
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).