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: Thu, 21 Jun 2018 08:54:09 -0700 [thread overview]
Message-ID: <20180621155409.GH2727@intel.com> (raw)
In-Reply-To: 20180613175748.GG2727@intel.com
[-- Attachment #1: Type: text/plain, Size: 2908 bytes --]
On Wed, Jun 13, 2018 at 10:57:48AM -0700, Philip Tricca wrote:
> On Tue, Jun 05, 2018 at 12:17:42PM -0700, Philip Tricca wrote:
> > On Mon, May 21, 2018 at 07:12:11PM -0700, Philip Tricca wrote:
> > > 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
> >
> > RC3 was just tagged and signed. This RC got held up while we sorted out
> > how to best deal with the active PCR bank issue identified with the
> > latest simulator rlease and VMWare. The solution implemented is what we
> > think is the best for compatibility and "future-proofing".
> >
> > This RC can be found here:
> > https://github.com/tpm2-software/tpm2-tss/releases/tag/2.0.0_rc3
>
> Another week, another RC. This time it's RC4. This one was prompted by
> another bug-fix in in the ESYS API. The commit hash for the fix is:
> 19f7007b9ec0d8d44bd755ee4967d6bf54d2af8f. Since this fix warranted
> another RC I've gone back through the PR queue merging everything that
> was reviewed during the RC3 window.
>
> This latest RC can be found here:
> https://github.com/tpm2-software/tpm2-tss/releases/tag/2.0.0_rc4
The RC4 window was pretty quiet thankfully. The only significant change
we took in added a missing '#include' directive to the tcti-mssim.c
source file:
https://github.com/tpm2-software/tpm2-tss/commit/171612924a627e73d6c826efb8706587bec69060
Given that we've already been through 5 RCs and this one change during
RC4 is pretty minor I'm satisfied that we're ready for the 2.0.0
release! The final changes to version numbers and the CHANGELOG.md are
done, the 2.0.0 tag has been signed and the release artifacts uploaded
to github: https://github.com/tpm2-software/tpm2-tss/releases/tag/2.0.0
Please go grab the tarball and give the release as much testing as you
can. Many thanks to everyone who contributed code, tests, testing,
documentation and everything else that's gone into this release.
Regards,
Philip
next reply other threads:[~2018-06-21 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 15:54 Philip Tricca [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-13 17:57 [tpm2] tpm2-tss 2.0.0 release candidate 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-22 2:12 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=20180621155409.GH2727@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 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.