From: Philip Tricca <flihp at twobit.us>
To: tpm2@lists.01.org
Subject: Re: [tpm2] tpm2.0-tools: Release 2.1.0 is available
Date: Mon, 25 Sep 2017 15:28:41 -0700 [thread overview]
Message-ID: <1506378521.8771.53.camel@twobit.us> (raw)
In-Reply-To: 2ce17cef-4c05-427a-81a7-2c5fc80d047f@redhat.com
[-- Attachment #1: Type: text/plain, Size: 2102 bytes --]
On Fri, 2017-09-22 at 13:26 +0200, Javier Martinez Canillas wrote:
> Hello Bill and Philip,
>
> On 08/16/2017 11:45 AM, fmartine(a)redhat.com wrote:
> > On 08/14/2017 09:38 PM, Roberts, William C wrote:
>
> [snip]
>
> > > > >
> > > > > I'm asking because there is a bunch of new stuff and fixes
> > > > > currently
> > > > > in master, so it would be nice to start thinking on the next
> > > > > release:
> > > > >
> > > > > $ git lg 2.1.0..master | wc -l
> > > > > 221
> > > > >
> > > >
> > > > Any comments on this?
> > >
> > > Sorry I missed this, somehow. 3.0 is tentatively scheduled in
> > > Sept/Oct, but I want to
> > > Coordinate this with the next version of tss, so I can pull in
> > > any of the API incompatible
> > > changes. So I am actually going to block the next major release
> > > of tools on tss based on
> > > my understanding with Phillip.
> > >
>
> Do you have a better idea about when the next tpm2-tss and tpm2-tools
> releases
> may happen? The reason why of the nagging, is because as mentioned I
> have a PR
> for the Clevis project [0] that is using the latest stuff from tpm2-
> tools next.
I had a chance to talk to some of the RedHat folks about Clevis @ the
plumbers conference earlier this month. Interesting & exciting stuff.
The next release of the tools doesn't depend on a new release of the
TSS libraries so that should be off the critical path. The tools
release is however blocked on a bug in the tabrmd. This is my next work
item.
> But the problem is that we can't merge it until there's a release of
> tpm2-tools
> that contains those changes.
With the tools blocked on the tabrmd we'll be doing a release of the
two in tandem. I'm expecing that the work I've signed up for there to
be on the order of "a few weeks". So while I'm always hesitant to state
release goals publicly I think this can be ready for a release toward
the end of October. Can't make any guarantees but that's our goal.
Best,
Philip
>
> [0]: https://github.com/latchset/clevis/pull/17
>
> Best regards,
next reply other threads:[~2017-09-25 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 22:28 Philip Tricca [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-26 20:09 [tpm2] tpm2.0-tools: Release 2.1.0 is available Javier Martinez Canillas
2017-09-22 11:26 Javier Martinez Canillas
2017-08-16 9:45 Javier Martinez Canillas
2017-08-14 19:38 Roberts, William C
2017-08-10 14:43 Javier Martinez Canillas
2017-08-02 10:04 Javier Martinez Canillas
2017-07-24 17:54 Roberts, William C
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=1506378521.8771.53.camel@twobit.us \
--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