From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 16/04/2020
Date: Thu, 16 Apr 2020 12:21:10 +0100 [thread overview]
Message-ID: <5e03f022-c03e-f90c-c9c3-e1b66f473cd6@intel.com> (raw)
In-Reply-To: <3282554.2IRrRt1zHL@thomas>
On 4/16/2020 11:49 AM, Thomas Monjalon wrote:
> 16/04/2020 12:06, Ferruh Yigit:
>> * Marvell, Arm, Mellanox & Broadcom already sent roadmap for 20.05, all
>> vendors please share the roadmap for the release.
>
> I think it is too late now for 20.05 roadmap :-)
>
>> Subtrees
>> --------
>>
>> * main
>> * There are still lots of patches, a lot of reviews are missing
>> * Sub-trees will be pulled next week Monday/Tuesday
>> * Sub-trees should be ready by EOD Friday or Saturday
>> * Thomas did review on graph library, planning to get it as it is
>
> No I did not review rte_graph.
> But as it is here for long, it should be merged.
>
>> * Trace library will be merged for -rc1, the review was missing but at least
>> feedback requested
>
> David worked on rte_trace reviews.
> More reviews were expected.
> We hope there will be more feedback after the merge as experimental.
> Please let's have open feedback, don't be shy asking for rework
> if you have any enhancement idea.
>
>> * Some library features may go in for -rc2 due to big backlog
>
> We will try to minimize feature additions in -rc2 if any.
>
>> * If the work is not finished, planning to block related patches
>> * Example: ABI breaks for false positive, don't get patches that
>> breaks ABI before fixing the ABI check tools.
>
> Yes we should block patches more often to get work done.
> We can find other examples in crypto or ethdev.
> We need to define clear deadlines.
> Example: any patch in a PMD will be blocked after a deadline
> if the PMD does not comply with the requested rework,
> as RTE_ETH_DEV_CLOSE_REMOVE behaviour.
>
>> * next-net
>> * Less than 50 patches in the backlog
>> * Some ethdev patches are not merged yet, close but not ready for -rc1
>> * mlx set that break the ABI not clarified yet, it may be dropped from tree
>>
>> * next-crypto
>> * ~50 patches in backlog, reviewed most of them, will apply today
>> * ipsec patch depends on hash change which is for main repo
>> * Thomas will look to it with priority
>
> It seems hash patches are not ready or not reviewed.
>
>> * ABI related crypto patch will be reviewed today
>> * There is a reported build error from Raslan
>
> Looks to be not reproduced.
I think this may be valid issue, but reproduced randomly, because in make build,
the ipsec dependency to hash library looks missing.
>
> [...]
>> * 18.11.7 released
>> * http://inbox.dpdk.org/dev/20200415173701.19706-1-ktraynor@redhat.com/
>
> Congratulations Kevin!
>
>
>
prev parent reply other threads:[~2020-04-16 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 10:06 Ferruh Yigit
2020-04-16 10:49 ` Thomas Monjalon
2020-04-16 11:21 ` Ferruh Yigit [this message]
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=5e03f022-c03e-f90c-c9c3-e1b66f473cd6@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).