Hello tpm2 list,
No doubt you all have noticed the increasing churn in our source tree
over the last few weeks. We’ve added some much needed features like the
new TCTI initialization mechanism that we’re now working to standardize
as well as the re-write of our logging infrastructure thanks to a
generous contribution from @AndreasFuchsSIT. In the run up to our next
major release that we’re planning for “around March” you can expect
additional churn much of which will *not* be backward compatible.
In an attempt to keep all affected parties informed we’ve been laying
out our planned work in the per-repo Github issue trackers. We’re
organizing related tasks / issue into ‘milestones’ and aligning the
milestones with our planned releases. The milestones currently scheduled
for our 2.0 release all have the ‘due-date’ field set accordingly:
. Similar milestones have
been created for the tpm2-tools and tpm2-abrmd for the same purpose.
Finally, we’ve established a new Github organization dedicated to the
tss2 effort and will be migrating the 3 repos to it over the next few
days. The purpose of this new org is to foster the continued growth of
this fledgling project and to encourage wider engagement with the community.
The migration to this new org should be completed in the next few days.
Happy new year,