From: Ferruh Yigit <ferruh.yigit@intel.com>
To: oulijun <oulijun@huawei.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 3/12/2020
Date: Mon, 7 Dec 2020 12:31:15 +0000 [thread overview]
Message-ID: <45cbb41b-15d3-ff77-e4da-8b808960cc69@intel.com> (raw)
In-Reply-To: <31c39b32-18a7-7396-7b82-f5bb0f970e35@huawei.com>
On 12/7/2020 11:54 AM, oulijun wrote:
>
>
> 在 2020/12/3 19:51, Ferruh Yigit 写道:
>> Meeting minutes of 3 December 2020
>> ----------------------------------
>>
>> Agenda:
>> * Release Dates
>> * 20.11 retrospective
>> * LTS
>> * OvS
>> * Opens
>>
>> Participants:
>> * Arm
>> * Debian/Microsoft
>> * Intel
>> * Nvidia
>> * NXP
>> * Red Hat
>>
>>
>> Release Dates
>> -------------
>>
>> * v20.11 is released on Friday, 27 November 2020
>> * https://mails.dpdk.org/archives/dev/2020-November/193684.html
>> * https://core.dpdk.org/download/
>> * https://doc.dpdk.org/guides/rel_notes/release_20_11.html
>>
>> * This was the biggest ever DPDK release, thanks to everyone who contributed.
>>
>> * v21.02 dates
>> * Proposal/V1: Sunday, 20 December 2020
>> * -rc1: Friday, 15 January 2021
>> * Release: Friday, 5 February 2021
>>
>> * Please send roadmaps, preferably before beginning of the release
>> * Thanks to NTT for sending roadmap
>>
> Hi, Ferruh Yigit
> We plan to send the roadmap, but we're not sure what it requires? Is it per
> vendor or per PMD vendor? What should he contain?
>
There is no strict formatting for it, the intention is to document the work
planned for the coming release, it is sent per vendor mostly. Following are the
past a few ones you can check as samples:
arm:
http://inbox.dpdk.org/dev/DBAPR08MB58147BA5F6A1D90B702592C498240@DBAPR08MB5814.eurprd08.prod.outlook.com/
broadcom:
http://inbox.dpdk.org/dev/CACZ4nhvDnB49YK_4SMH=BDAoRntgXxyW4kjpcpdqwHuGpwwOGg@mail.gmail.com/
nvidia:
http://inbox.dpdk.org/dev/DM5PR12MB2406E0A8CC7C6E884B770B02CD560@DM5PR12MB2406.namprd12.prod.outlook.com/
marvell:
http://inbox.dpdk.org/dev/BYAPR18MB2424F954434930AEF34CBD0AC8590@BYAPR18MB2424.namprd18.prod.outlook.com/
intel: http://inbox.dpdk.org/dev/20200612135804.3781756-1-ferruh.yigit@intel.com/
> Thanks
> Lijun Ou
>>
>> 20.11 retrospective
>> -------------------
>>
>> (I tried to summarize as best as I can, please free to correct/add when needed)
>>
>> * What went well
>> * Managed to get out this very big release on time
>> * Was more precise with dates
>> * Expectations on features were more clear in this release
>> * Good co-working between maintainers
>> * Communication was better, project become more resilient
>> * Akhil commented last minute stress was less
>> * Major gcc distribution didn't cause disruption this time
>> * LTS is doing good job overall
>> * Thanks to Luca and Kevin for their work there
>>
>> * Things to improve
>> * next-net is busy, %60+ of the commits coming from next-net,
>> would be good to get more help, options to improve
>> * Add a co-maintainer in that level
>> * Andrew (backup maintainer) is great candidate if he can spare time
>> He is already helping on reviews
>> * He already covered during release when Ferruh is on holiday
>> * Testpmd maintainership is not working fine, find maintainers for it
>> * Should we add more vendor trees?
>> * Huawei is contributing more, should it have a vendor sub-tree?
>> * Huawei is being good citizen mostly
>> * CI can be improved
>> * Top level Thomas/David may felt the last minute stress more this time
>> * Pachwork update by Jerin, to add reviewer column may help
>> * This seems not exactly matching patchwork intention of using delegate
>> field
>> * Need to work on how to upstream this improvement
>> * It is causing more problem when expectation is not clear from vendors
>> * Security issues
>> * They didn't work very well, the busy release is affecting it
>> * Good thing is there is a well defined process, needs resource to execute
>> * Can help to allocate separate resource for it
>> * A technical project manager can do it, doesn't have to be developer
>>
>>
>> LTS
>> ---
>>
>> * v19.11.6-rc1 is out, please test
>> * http://inbox.dpdk.org/dev/20201203093856.299103-1-luca.boccassi@gmail.com/
>> * Target release date is 17 December
>>
>> * v18.11.10 work is going on
>> * waiting for backports, request emails sent
>> * -rc1 is planned before holidays
>>
>>
>> OvS
>> ---
>>
>> * Second version of patch to switch DPDK 20.11 is sent, please review
>>
>>
>> Opens
>> -----
>>
>> * Asaf shared a draft release process documentation
>> * It will be sent as documentation patch for community review,
>> after initial review
>>
>>
>>
>> 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 every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK
>>
>> If you wish to attend just send an email to
>> "John McNamara <john.mcnamara@intel.com>" for the invite.
>> .
>>
next prev parent reply other threads:[~2020-12-07 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 11:51 Ferruh Yigit
2020-12-07 11:54 ` oulijun
2020-12-07 12:31 ` Ferruh Yigit [this message]
2020-12-07 13:03 ` oulijun
2020-12-07 13:59 ` Ferruh Yigit
2020-12-07 14:48 ` oulijun
Reply instructions:
You may reply publicly 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 \
--in-reply-to=45cbb41b-15d3-ff77-e4da-8b808960cc69@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=oulijun@huawei.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).