From: Ferruh Yigit <email@example.com> To: dpdk-dev <firstname.lastname@example.org> Cc: Thomas Monjalon <email@example.com> Subject: [dpdk-dev] DPDK Release Status Meeting 16/01/2020 Date: Thu, 16 Jan 2020 11:13:52 +0000 Message-ID: <firstname.lastname@example.org> (raw) Minutes 16 January 2020 ----------------------- Agenda: * Release Dates * Subtrees * OvS Participants: * Debian/Microsoft * Intel * Marvell * Mellanox * NXP * Red Hat Release Dates ------------- * v20.02 dates: * Integration deadline passed, it was on Wednesday 15 January 2020 * RC1 is expected before the weekend, possibly on Friday 17 January * PRC holidays on 24-20 Jan (inclusive) * Release: Friday 14 February 2020 * v20.05 proposal: * Proposal/V1: Friday 6 March 2020 * Integration/Merge/RC1: Friday 10 April 2020 * Release: Friday 1 May || Wed 13 May * 1-5 May holiday on PRC, we need to do the release before or after that Please comment on between 1 May or 13 May. Subtrees -------- * main * Will try to do -rc1 before Monday with best effort * Two series from arm * "ring library" updates * May go in in this release * Use WFE for aarch64 * ABI tooling patches * Tech-board selected David's approach * Automated checks will be in CI after David's patch * We need automated checks to be sure we are not breaking the ABI otherwise it is not always easy for developer to catch the break * Waiting new version of Neil's __rte_internal pathcset * next-net * Almost all ethdev changes merged, planning to finalize last remaining 1-2 ones today * All sub-trees pulled except some mlx and brcm one that are waiting fix * Some PMD patches may be postponed to -rc2 * next-net-crypto * Pull request sent * There is a performance concern on some ipsec-gw patches, they can go in -rc2 if the issue is solved * CPU crypto from last release may be breaking ABI, need to confirm and discussed dummy variable is missing, may be postponed to next release * Some PMD changes are postponed to -rc2 * next-net-eventdev * Pull request sent, it is a small set * next-net-virtio * All commit pulled to next-net * virtio vDPA drive will be postponed to next release * Some patches waiting user change and some are under review * Can be some more patches for -rc2 * next-net-intel * Nothing critical, most of the patches have been pulled * 'fm10k' patches are not reviewed, may go in -rc2 if reviewed otherwise will be postponed to next release * LTS * 17.11.10-rc1 released, please test and report results * https://mails.dpdk.org/archives/dev/2020-January/154915.html * Release planned on January / February * 18.11.6-rc2 released, please test and report results * https://mails.dpdk.org/archives/dev/2020-January/155132.html * Only a few patches on top of -rc1 * Intel will plan a validation, it won't be full validation * Release planned on 31st January OvS --- * Using DPDK experimental APIs discussed, it is accepted to use once as exception, so feature won't be blocked * DPDK need to figure out how to backport removing experimental tags to the LTS releases 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 <email@example.com>" for the invite.
next reply index Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-16 11:13 Ferruh Yigit [this message] 2020-01-16 12:48 ` Ananyev, Konstantin 2020-01-16 13:17 ` Akhil Goyal 2020-01-16 13:39 ` Ananyev, Konstantin 2020-01-16 16:42 ` Akhil Goyal 2020-01-16 17:47 ` Ferruh Yigit 2020-01-16 13:19 ` Akhil Goyal 2020-01-16 17:50 ` Ferruh Yigit 2020-01-17 16:00 ` Honnappa Nagarahalli 2020-01-17 11:39 Ananyev, Konstantin
Reply instructions: You may reply publically to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
DPDK-dev Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/dpdk-dev/0 dpdk-dev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 dpdk-dev dpdk-dev/ https://lore.kernel.org/dpdk-dev \ firstname.lastname@example.org public-inbox-index dpdk-dev Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.dpdk.dev AGPL code for this site: git clone https://public-inbox.org/public-inbox.git