Minutes 7 February 2019 ----------------------- Agenda: * Release Dates * Subtrees * OvS * Opens
Participants: * Debian * Intel * Mellanox * RedHat Release Dates ------------- * v19.02 released: * https://core.dpdk.org/download/ * https://doc.dpdk.org/guides/rel_notes/release_19_02.html * v19.05 dates: * Proposal Deadline: Friday, 1 March * RC1: Friday, 29 March * Release: Friday, 10 May * Schedule web page updated accordingly: http://core.dpdk.org/roadmap/#dates * Contributors please provide 19.05 roadmap whenever available * Intel & Mellanox working on sending one soon. Arm? RedHat? NXP? Marvel? others? Subtrees -------- * main * Intel will provide list of acked patches for early merge for release * next-net * next-virtio * next-crypto * No new patch on the tree * next-eventdev * next-pipeline * next-qos * No update, we need attendance from maintainers * Stable trees * Stable tree RC waiting for test, anyone from community welcome to test them send a test report or even a quick note to mail list: * LTS: v16.11.9-rc2 * LTS: v17.11.5-rc2 * Stable: v18.08.1-rc3 * Reminder, each stable managed as a branch on stable git tree: https://git.dpdk.org/dpdk-stable/ * Can be good to provide more detailed information on what has been tested, like which libraries, in test reports * If there is good enough coverage of test reports received, stable tree can be released * CI should help testing stable trees, no update yet from DPDK community lab LTS testing request OvS --- * In progress, no issue seen on 2.11 * Bug fix phase * OvS can help testing DPDK LTS release candidates Opens ----- * Akhil is looking for co-maintainer for crypto sub-tree, any volunteer please contact to Akhil or Thomas. 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.mcnam...@intel.com>" for the invite.