From: Nicolas Morey <nmorey@suse.com>
To: Mark Haywood <mark.haywood@oracle.com>, linux-rdma@vger.kernel.org
Subject: Re: [ANNOUNCE] rdma-core: new stable releases
Date: Thu, 28 Sep 2023 19:49:21 +0200 [thread overview]
Message-ID: <cf5c0c73-46dc-4091-a578-262d7629f85f@suse.com> (raw)
In-Reply-To: <7659c824-ad3e-eb6c-1928-fd438fa68e70@oracle.com>
On 9/28/23 17:39, Mark Haywood wrote:
> I see v48.0 was tagged. Is it not a stable release?
>
> Thanks.
> Mark
>
What is called stable releases here, are released based on a vXX.0 tag where fixes from newer releases are backported.
But yes, v48.0 is a stable release in the sense it is a working release :)
Nicolas
next prev parent reply other threads:[~2023-09-28 17:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 13:55 [ANNOUNCE] rdma-core: new stable releases Nicolas Morey
2023-09-28 15:39 ` Mark Haywood
2023-09-28 17:49 ` Nicolas Morey [this message]
2023-09-28 19:02 ` Mark Haywood
-- strict thread matches above, loose matches on Subject: below --
2026-01-07 9:14 Nicolas Morey
2025-06-17 13:19 Nicolas Morey
2025-04-03 10:40 Nicolas Morey
2025-01-22 17:06 Nicolas Morey
2024-10-08 14:18 Nicolas Morey
2024-05-29 18:23 Nicolas Morey
2024-01-22 18:33 Nicolas Morey
2024-01-24 22:05 ` Aron Silverton
2024-01-25 10:25 ` Leon Romanovsky
2024-05-29 18:33 ` Nicolas Morey
2023-07-18 10:55 Nicolas Morey
2023-06-09 12:10 Nicolas Morey
2023-03-20 21:28 Nicolas Morey
2023-03-21 8:05 ` Leon Romanovsky
2022-10-24 10:31 Nicolas Morey-Chaisemartin
2022-01-07 11:05 Nicolas Morey-Chaisemartin
2021-10-15 11:39 Nicolas Morey-Chaisemartin
2021-06-03 14:47 Nicolas Morey-Chaisemartin
2021-01-27 17:25 Nicolas Morey-Chaisemartin
2020-11-04 10:17 Nicolas Morey-Chaisemartin
2020-04-14 11:40 Nicolas Morey-Chaisemartin
2019-11-28 14:18 Nicolas Morey-Chaisemartin
2019-09-26 13:59 Nicolas Morey-Chaisemartin
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=cf5c0c73-46dc-4091-a578-262d7629f85f@suse.com \
--to=nmorey@suse.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mark.haywood@oracle.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