Proposal for Notation v2.x plan

[yizha1]

Here is the proposal for Notation v2.x plan:

Milestone Notation v2.0.0

Target Date: Mar 2025
Main enhancements:

• Update the default behavior to use the OCI-1.1 specification when storing signatures. #1040
• Notation to sign and verify arbitrary data #741
• Check whether the detached signature file meets the OpenSSF Scorecard check criteria or not #974

Milestone Notation v2.1.0

Target date: Jun 2025
Main enhancements:

• Support more wildcards in trust policy #476
• Attestations #1067

[github-actions]

This issue is stale because it has been opened for 60 days with no activity. Remove stale label or comment. Otherwise, it will be closed in 30 days.

[github-actions]

This issue is stale because it has been opened for 60 days with no activity. Remove stale label or comment. Otherwise, it will be closed in 30 days.

[FeynmanZhou]

@yizha1 This proposal is more like an open discussion for the community. It's hard to move it to a specific milestone. Would you mind if we transfer it to the GitHub Discussion?

I used to create this kind of discussion in other projects like ORAS oras-project/oras#1119

[yizha1]

@FeynmanZhou Using issues not dicussions is the way that are aligned with the community previously. As dicussions are not actively triaged or followed. That is the reason why v2.x plan was created as an issue, you can find issues that we created previously for other releases.

We can close this issue, if no further action is required. As once we are aligned on releases scopes and timeline, we can update the milestones and close the issue accordingly.