Hi Mimi, ... > > > Also, having docker based travis setup helps to test build against other distros > > > (we have it in LTP). > The existing travis.yml is a first attempt at using travis. (Hint: > help with cleaning it up would be much appreciated.) Should this > travis.yml be included now in 1.3.1 or deferred to 1.3.2? Let's sync > up on what should be included when. Additional suggestions are > welcome. > 1.3.1 release (~1 week): > - minor fixes > Proposed 1.3.2 features (~3 months): > - Travis integration > - Support providing the TPM 2.0 PCRs as a file (--pcrs option). > - Walking the TPM 2.0 event log as the basis for calculating the > "boot_aggregate". Thank you for sharing your roadmap. I'd vote for sooner include (it's not set in the stone, it can be changed later :)), but up to you. Not sure if I have enough time to significantly help with Travis, I'll try. That docker based testing is nice, because it's a testing on real distro. > thanks, > Mimi Kind regards, Petr
