From: Ray Kinsella <mdr@ashroe.eu>
To: David Marchand <david.marchand@redhat.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, dev <dev@dpdk.org>,
Aaron Conole <aconole@redhat.com>,
Michael Santana <maicolgabriel@hotmail.com>
Subject: Re: [PATCH] version: 22.07-rc0
Date: Tue, 22 Mar 2022 05:15:38 -0400 [thread overview]
Message-ID: <87v8w6qret.fsf@mdr78.vserver.site> (raw)
In-Reply-To: <CAJFAV8w+=JJQpAWkoPi6kFkX1FCadjvAV9MW6oUE_UD-t9johw@mail.gmail.com>
David Marchand <david.marchand@redhat.com> writes:
> On Mon, Mar 21, 2022 at 2:01 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>>
>> 18/03/2022 15:35, David Marchand:
>> > +ABI Changes
>> > +-----------
>> > +
>> > +.. This section should contain ABI changes. Sample format:
>> > +
>> > + * sample: Add a short 1-2 sentence description of the ABI change
>> > + which was announced in the previous releases and made in this release.
>> > + Start with a scope label like "ethdev:".
>> > + Use fixed width quotes for ``function_names`` or ``struct_names``.
>> > + Use the past tense.
>> > +
>> > + This section is a comment. Do not overwrite or remove it.
>> > + Also, make sure to start the actual text at the margin.
>> > + =======================================================
>> > +
>> > +* No ABI change that would break compatibility with 21.11.
>>
>> Should we say 21.11 and 22.03?
>
> In practice, compatibility is probably maintained, but we are
> committed to maintain ABI compatibility with v21.11 only.
> So I would leave this as is.
>
> http://inbox.dpdk.org/dev/27c97b09-0b78-ccbc-db1e-860ac6012aec@ashroe.eu/
Agreed +1 - our only commitment is to v21.11.
Otherwise things would start to get very complicated. :-)
--
Regards, Ray K
next prev parent reply other threads:[~2022-03-22 9:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 14:35 [PATCH] version: 22.07-rc0 David Marchand
2022-03-18 15:46 ` Aaron Conole
2022-03-21 15:41 ` Thomas Monjalon
2022-03-21 13:01 ` Thomas Monjalon
2022-03-21 14:09 ` David Marchand
2022-03-22 9:15 ` Ray Kinsella [this message]
2022-03-22 10:35 ` Thomas Monjalon
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=87v8w6qret.fsf@mdr78.vserver.site \
--to=mdr@ashroe.eu \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.