From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: dpdklab <dpdklab@iol.unh.edu>, ci@dpdk.org, dev <dev@dpdk.org>,
Aaron Conole <aconole@redhat.com>,
Michael Santana <maicolgabriel@hotmail.com>,
Ray Kinsella <mdr@ashroe.eu>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] version: 22.11-rc0
Date: Mon, 18 Jul 2022 12:21:37 -0400 [thread overview]
Message-ID: <CAOE1vsOgjz88qs=WrezSoek+y=WEYE-jNkLgETvyOYU-yOmzyg@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8yN4gQawm2agUyFbnPvYoE9_s4SV8oqYTeTfu_RofBGLQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
HI All,
With the 22.07 release, I think we can now disable the ABI for the dpdk
main, until the next LTS release, correct?
Cheers,
Lincoln
On Mon, Jul 18, 2022 at 8:34 AM David Marchand <david.marchand@redhat.com>
wrote:
> Hello CI guys,
>
> On Mon, Jul 18, 2022 at 12:10 PM David Marchand
> <david.marchand@redhat.com> wrote:
> >
> > Start a new release cycle with empty release notes.
> >
> > The ABI version becomes 23.0.
> > The map files are updated to the new ABI major number (23).
> > The ABI exceptions are dropped and CI ABI checks are disabled because
> > compatibility is not preserved.
> > Special handling of removed drivers is also dropped in check-abi.sh and
> > a note has been added in libabigail.abignore as a reminder.
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
>
> Just a heads-up that once this patch is merged, the ABI check will
> have to be disabled in CI environments.
>
>
> --
> David Marchand
>
>
--
*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: 2674 bytes --]
next prev parent reply other threads:[~2022-07-18 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220718100909.2299331-1-david.marchand@redhat.com>
2022-07-18 12:34 ` David Marchand
2022-07-18 16:21 ` Lincoln Lavoie [this message]
2022-07-19 10:35 ` David Marchand
2022-07-19 12:04 ` Lincoln Lavoie
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='CAOE1vsOgjz88qs=WrezSoek+y=WEYE-jNkLgETvyOYU-yOmzyg@mail.gmail.com' \
--to=lylavoie@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=maicolgabriel@hotmail.com \
--cc=mdr@ashroe.eu \
--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).