From: Chuck Lever <chuck.lever@oracle.com>
To: kernel-tls-handshake <kernel-tls-handshake@lists.linux.dev>
Subject: Re: Preparing for ktls-utils-1.0
Date: Thu, 6 Feb 2025 11:41:51 -0500 [thread overview]
Message-ID: <3f33cfa8-edfc-4cde-8c42-5083eb405fc3@oracle.com> (raw)
In-Reply-To: <c6d66de9-f66a-475a-bf63-ae5eb15ea85a@oracle.com>
On 1/29/25 3:03 PM, Chuck Lever wrote:
> On 1/29/25 9:39 AM, Chuck Lever wrote:
>> I received a request to publish a fresh release of ktls-utils.
>> My thought was this is an opportunity to release a 1.0.
>>
>> I can request a Parfait run on the current source code.
After reviewing some old email, looks like the Parfait runs are
now automatic and weekly, so no request was necessary.
>> I've
>> never gotten Coverity to work. Any other analysis tools we
>> can try?
>>
>> Are there any other features that should be in this release?
>
> It would be great to close these two before a 1.0 release.
>
> - https://github.com/oracle/ktls-utils/issues/21
>
> - https://github.com/oracle/ktls-utils/issues/71
>
>
>> All code review (or re-review) is welcome.
Hannes closed #71. #21 is still pending, but I don't view it as a
release blocker.
I've created a pre-release of ktls-utils-1.0:
https://github.com/oracle/ktls-utils/releases/tag/ktls-utils-1.0-rc1
Let me know if something is missing or broken.
--
Chuck Lever
prev parent reply other threads:[~2025-02-06 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 14:39 Preparing for ktls-utils-1.0 Chuck Lever
2025-01-29 20:03 ` Chuck Lever
2025-02-06 16:41 ` Chuck Lever [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=3f33cfa8-edfc-4cde-8c42-5083eb405fc3@oracle.com \
--to=chuck.lever@oracle.com \
--cc=kernel-tls-handshake@lists.linux.dev \
/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.