TPM2 (Trusted Platform Module) userspace development
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm at redhat.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] tpm2-tss v2.2.0
Date: Wed, 06 Feb 2019 01:21:09 +0100	[thread overview]
Message-ID: <6ee9d456-9a2b-3b69-c90c-05037e64f998@redhat.com> (raw)
In-Reply-To: 4ced1f47-62ab-457b-0e6e-46f7e5de147a@intel.com

[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]

Hello Tadeusz,

On 2/5/19 6:55 PM, Tadeusz Struk wrote:
> Hi Javier,
> 
> On 2/4/19 11:36 PM, Javier Martinez Canillas wrote:
>> 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.
> 
> Yes, the logic is that the first number changes if there are changes that
> break backwards compatibility. The second number bumps if that are new
> features, but the release does not break backward compatibility, and
> the last number is just for bug fixes. So it is safe to update from 2.1.1
> to 2.2.0. As you noted - it includes bug fixes and the two new features.
> The 2.1.1 version is for users who, for whatever reason, do not want to
> have the new features, but want to get all the bug fixes. Similar story
> with 2.0.2.
> I imagine that for 2.0.x and 2.1.x we will maintain them for one year
> after the initial release, and only release new version if there will
> be explicit ask for it from the users.
> 
> The numbering method is described in
> https://github.com/tpm2-software/tpm2-tss/blob/master/RELEASE.md#version-numbers
> 

Thanks a lot for the clarification. I've updated the package to 2.2.0.

Best regards,
-- 
Javier Martinez Canillas
Software Engineer - Desktop Hardware Enablement
Red Hat

             reply	other threads:[~2019-02-06  0:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06  0:21 Javier Martinez Canillas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-05 17:55 [tpm2] tpm2-tss v2.2.0 Tadeusz Struk
2019-02-05  7:36 Javier Martinez Canillas
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=6ee9d456-9a2b-3b69-c90c-05037e64f998@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