From: Philip Tricca <philip.b.tricca at intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] tpm2-tss 2.0.0 release candidate
Date: Mon, 21 May 2018 19:12:11 -0700 [thread overview]
Message-ID: <20180522021211.GE26060@intel.com> (raw)
In-Reply-To: 20180521230413.GD26060@intel.com
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
On Mon, May 21, 2018 at 04:04:13PM -0700, Philip Tricca wrote:
> On Fri, May 11, 2018 at 04:18:41PM -0700, Philip Tricca wrote:
> > Hello again,
> >
> > On Fri, May 04, 2018 at 03:44:15PM -0700, Philip Tricca wrote:
> > > The first release candidate for version 2.0.0 was just tagged. Please
> > > take whatever time you can spare to give it some testing.
> > > https://github.com/tpm2-software/tpm2-tss/releases/tag/2.0.0_rc0
> >
> > A few minor fixes during the RC0 window: specifically two fixes for issues
> > identified by static analysis / coverity. These were merged yesterday
> > and RC1 tagged today.
>
> During the RC1 window Tadeusz identified a number of issues one of which
> affected the public API. As a result RC2 was just tagged and we're
> kicking off another review window for the next week.
Forgot the link:
https://github.com/tpm2-software/tpm2-tss/releases/tag/2.0.0_rc2
Philip
next reply other threads:[~2018-05-22 2:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 2:12 Philip Tricca [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-21 15:54 [tpm2] tpm2-tss 2.0.0 release candidate Philip Tricca
2018-06-13 17:57 Philip Tricca
2018-06-06 21:29 Trevor Woerner
2018-06-06 21:17 Philip Tricca
2018-06-06 13:18 Trevor Woerner
2018-06-05 19:17 Philip Tricca
2018-05-21 23:04 Philip Tricca
2018-05-11 23:18 Philip Tricca
2018-05-04 22:44 Philip Tricca
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=20180522021211.GE26060@intel.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