From: Javier Martinez Canillas <javierm at redhat.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] tpm2-tss v2.2.0
Date: Tue, 05 Feb 2019 08:36:41 +0100 [thread overview]
Message-ID: <215e4114-07d2-7875-47fa-727b35b2634b@redhat.com> (raw)
In-Reply-To: 9e582c6b-dc7c-0395-e0fc-56875ed73c2c@intel.com
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
Hello Tadeusz,
On 2/5/19 1:02 AM, Tadeusz Struk wrote:
> Hello,
> I'm happy to announce that the tpm2-tss v2.2.0 is out. It can be found here:
>
> https://github.com/tpm2-software/tpm2-tss/releases/tag/2.2.0
>
> All changes and fixed issues are listed in the CHANGELOG.md file.
>
Thanks a lot for the releases and the announcements. I've a maybe silly
question but it wasn't clear to me why we have both a 2.1.1 and 2.2.0
releases. From the CHANGELOG it seems that the only difference is that
2.2.0 has new features (QNX build and dev TCTI partial reads support)
while 2.1.1 only contains the fixes.
Does it mean that it's safe to update the Fedora package from 2.1.0 to
2.2.0 or should I update to 2.1.1? My understanding is that the former.
I wonder if there's a lot of value in having too many 2.X releases or
if we should just stick with one, as long as there are no backward
incompatible changes. At least for me as a packager is confusing and
have to dig to understand the differences between all these releases.
For example in tpm2-tools we did have to do both 3.0.X and 3.X releases
because there was a non-backward compatible change between 3.0 and 3.1
(migration from tpm2-tss 1.4.0 to 2.0.0).
> Thanks,
>
Best regards,
--
Javier Martinez Canillas
Software Engineer - Desktop Hardware Enablement
Red Hat
next reply other threads:[~2019-02-05 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 7:36 Javier Martinez Canillas [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-06 0:21 [tpm2] tpm2-tss v2.2.0 Javier Martinez Canillas
2019-02-05 17:55 Tadeusz Struk
2019-02-05 0:02 Tadeusz Struk
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=215e4114-07d2-7875-47fa-727b35b2634b@redhat.com \
--to=tpm2@lists.01.org \
/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