From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: ci@dpdk.org
Subject: Re: [dpdk-ci] August 12 Community CI Minutes
Date: Fri, 13 Aug 2021 08:20:23 -0400 [thread overview]
Message-ID: <CAOE1vsM2YZiW06nLfNL1xeD56TP8XyTW4Us9xLiYL2AOshyT6A@mail.gmail.com> (raw)
In-Reply-To: <3155281.OWsgTbkY2n@thomas>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
Hi Thomas,
Just to make sure we understand correctly. We should turn off the ABI
runners for patches coming in between now and the release of 21.11 (since
21.08 is out). Once 21.11 is released, the ABI runners should be turned
back on and report failures again.
Cheers,
Lincoln
On Fri, Aug 13, 2021 at 2:08 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> 12/08/2021 16:40, Lincoln Lavoie:
> > * ABI references are now rebuilt and comparing against v21.08
>
> ABI should not be checked at all during 21.11 cycle
> because this release allows ABI breakages.
>
>
> > * Spell check patch (corrections to documentation) got merged, working
> on a
> > back port patch as well. Couple of new spelling errors were merged,
> Henry
> > is working on a patch for those as well.
>
> Thank you.
>
>
>
>
--
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>
[-- Attachment #2: Type: text/html, Size: 2302 bytes --]
next prev parent reply other threads:[~2021-08-13 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 14:40 Lincoln Lavoie
2021-08-12 14:47 ` Ali Alnubani
2021-08-12 15:04 ` Lincoln Lavoie
2021-08-13 6:07 ` Thomas Monjalon
2021-08-13 12:20 ` Lincoln Lavoie [this message]
2021-08-13 13:20 ` Thomas Monjalon
2021-08-13 16:21 ` Brandon Lo
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=CAOE1vsM2YZiW06nLfNL1xeD56TP8XyTW4Us9xLiYL2AOshyT6A@mail.gmail.com \
--to=lylavoie@iol.unh.edu \
--cc=ci@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).