From: Tricca, Philip B <philip.b.tricca at intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] tpm2-abrmd 2.1.0_rc0
Date: Wed, 06 Feb 2019 22:23:22 +0000 [thread overview]
Message-ID: <DB638850A6A2434A93ECADDA0BC838909CE35257@ORSMSX104.amr.corp.intel.com> (raw)
In-Reply-To: DB638850A6A2434A93ECADDA0BC838909CE336C1@ORSMSX104.amr.corp.intel.com
[-- Attachment #1: Type: text/plain, Size: 2101 bytes --]
A bit delayed by FOSDEM / travel but 2.1.0 has been tagged and signed: https://github.com/tpm2-software/tpm2-abrmd/releases/tag/2.1.0
Philip
From: tpm2 [mailto:tpm2-bounces(a)lists.01.org] On Behalf Of Tricca, Philip B
Sent: 28 January, 2019 15:02
To: 'tpm2(a)lists.01.org' <tpm2(a)lists.01.org>
Subject: Re: [tpm2] tpm2-abrmd 2.1.0_rc0
RC2 for the 2.1.0 release was just tagged. This includes a few small changes to make the build compatible with the latest autoconf-archive release and to eliminate a dependency on dbus-x11 from the automake test harness. Thanks to everyone who pushed me to get these changes into this release and apologies to everyone else for inflicting another RC cycle on you. I'll be at FOSDEM over the upcoming weekend so my plan is to sign the release Friday before the conference unless other issues come up.
RC2 is here: https://github.com/tpm2-software/tpm2-abrmd/releases/tag/2.1.0_rc2
Best,
Philip
From: tpm2 [mailto:tpm2-bounces(a)lists.01.org] On Behalf Of Tricca, Philip B
Sent: 23 January, 2019 10:58
To: 'tpm2(a)lists.01.org' <tpm2(a)lists.01.org<mailto:tpm2(a)lists.01.org>>
Subject: Re: [tpm2] tpm2-abrmd 2.1.0_rc0
The PR queue got a bit stuck between RC0 and RC1 on account of some changes upstream that broke the autobuilder. All sorted out now and the required changes are in RC1. This RC will likely be cut a bit short on account of how long RC0 took and some impending travel (FOSDEM!).
RC1 is here: https://github.com/tpm2-software/tpm2-abrmd/releases/tag/2.1.0_rc1
Best,
Philip
From: tpm2 [mailto:tpm2-bounces(a)lists.01.org] On Behalf Of Tricca, Philip B
Sent: 3 January, 2019 16:33
To: 'tpm2(a)lists.01.org' <tpm2(a)lists.01.org<mailto:tpm2(a)lists.01.org>>
Subject: [tpm2] tpm2-abrmd 2.1.0_rc0
Hello all,
We just tagged the first release candidate for version 2.1.0 of the tpm2-abrmd. The tag and relevant data can be found here: https://github.com/tpm2-software/tpm2-abrmd/releases/tag/2.1.0_rc0. Please create issues in github for any feedback you may have during the review period.
Thanks,
Philip
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 6648 bytes --]
next reply other threads:[~2019-02-06 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 22:23 Tricca, Philip B [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-28 23:01 [tpm2] tpm2-abrmd 2.1.0_rc0 Tricca, Philip B
2019-01-23 18:58 Tricca, Philip B
2019-01-04 0:33 Tricca, Philip B
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=DB638850A6A2434A93ECADDA0BC838909CE35257@ORSMSX104.amr.corp.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.