1.0 release

[jku]

I suppose we need an actual issue for this and not just the PR #767 .

Some possible blockers:

• docs: Remove pre 1.0 warnings (at least signer has one) EDIT: done docs: Remove pre 1.0.0 disclaimers #802
• docs: Document the Signer implementations (import methods, supported priv key urls, etc) in the reference docs docs: Include signer implementations in reference documentation #640
• docs: example app as documentation Create Example app #633
• annotations: actually annotate the API, add py,typed (see Release v??? #767 (comment))
• vaultsigner PR

I would say only the first one is really required.

[lukpueh]

I would say only the first one is really required.

Agreed. None of above breaks the API, so we could release it in the 1.x range. Though it could happen that we discover issues that do require a major bump, while working on docs and annotations. But I think that's okay.

[lukpueh]

FYI: in-toto now also has a preparatory PR for this (in-toto/in-toto#740). So on my end we are good to go.

[lukpueh]

There's one last minor clean-up PR, I'd like to get in before 1.0: #806