Release 1.0 planning

[lukehinds]

Items needed for release 1.0

• Sharding process and API changes. Cleanup some initialization/flag parsing in rekor-server. #433
• Documentation migrated / polished to docs.sigstore.dev
• Rename Ecosystem to Origin in Checkpoints [Formats] Rename Ecosystem checkpoint field to Origin google/trillian-examples#470 cc @bobcallaway
• Serve and upload SignedTimestamp based on Checkpoints

[asraa]

Adding some

• Rename Ecosystem to Origin in Checkpoints [Formats] Rename Ecosystem checkpoint field to Origin google/trillian-examples#470 cc @bobcallaway
• Serve and upload SignedTimestamp based on Checkpoints

[dlorenc]

Sharding stuff is ongoing! Ref #433

[cpanato]

I would like to add a cloudbuild + goreleaser when we release Rekor

then I have some questions:

1. We will use the same KMS key that we use to sign cosign? or we create another?
2. To push the data to the Rekor server how can we do that in an automated fashion way? there is any guide? or we just don't do it at this time?

@dlorenc @lukehinds @dekkagaijin

[cpanato]

And looks like we can review if we can make the v1.0.0 release soon, some PRs are already merged

[lukehinds]

I personally think we should be using keyless for signing as soon as we are ready. However we could use KMS as stop gap, if we can retro-sign previous releases using the fulcio root.

[naveensrinivasan]

This could be an issue #481 (comment) unless the project restricts/recommends/documents the size of the upload for 1.0 IMO.