---
tags: planning
---
# Notation v1.0.0-rc.1 release plan
## Goal
The goal of notation v1.0.0-rc.1 is to deliver fundamental signing and verifying experiences for end-users.

## Release scope

The current scope is tracked in [rc.1 user stories board](https://github.com/orgs/notaryproject/projects/10/views/10) and [rc.1 issues](https://github.com/orgs/notaryproject/projects/10/views/6), see below user stories for rc.1

| User Stories | Status | Cost Estimation | Comments |
| -------- | -------- | -------- | ------- |
| [Notation Sign Experience](https://github.com/notaryproject/roadmap/issues/40) | Pending | 2 weeks | It is mainly PM work to update CLI document by adding examples and verifying existing opitons. |
| [Notation verify - remote artifacts](https://github.com/notaryproject/roadmap/issues/41) | WIP | 1 week | New Verify CLI to use Trust policy and Trust store |
| [Notation plugin extensibility for sign and verify](https://github.com/notaryproject/notation/issues/240) | Done | 0 |
| [Notation plugin list](https://github.com/notaryproject/notation/issues/241) | Done | 0 |
| [Support COSE as signing envelope](https://github.com/notaryproject/roadmap/issues/7) | PR merge | 1-2 weeks code review | Development is done. Need review and merge PRs |
| [notation trust store experience via Notation cli commands](https://github.com/notaryproject/roadmap/issues/38) | WIP | 2 weeks | see notes-1 |
| [Test Case Automation for CLI Cmds](https://github.com/notaryproject/roadmap/issues/47)|Not Started | | Limited scope to Test framework plus sign and verify E2E flow|
|[Add --debug option to Notation CLI commands to help with troubleshooting and logging use cases](https://github.com/notaryproject/notation/issues/300)|Not Started|| Limited to sign and verify command |

> NOTES:
>1. According to [trust store and trust policy spec](https://github.com/notaryproject/notaryproject/blob/main/trust-store-trust-policy-specification.md), user need to copy certs into directories by following specific rules to use trust store, which is a cumbersome and error-prone process, not to mention multiple platform need to be supported. Strongly suggest to add CLI to manage trust store in rc.1. The first version of trust store CLI spec is ready, see [trust store CLI spec](https://hackmd.io/@yizha1/cli_trust_store). Regarding to manage trust policy in rc.1, user can manually update a JSON template file. We need to provide a guideline for it.

## Release Date

Based on the RC.1 scope and cost estimation above, the implementation is supposed to be completed **by the end of Sep, 2022**. Considering the PR review process and first week of Oct is the public holiday in China, the proposed official rc.1 release date is **by Week starting Oct 17, 2022**.