---
# System prepended metadata

title: New date proposed for notation rc.1 release

---

# New date proposed for notation rc.1 release

## Summary

- Total cost for code refactoring and rc.1 issues owned by MSFT 
    - implementation: `4 weeks` (starting from this week)
    - PR review efficiency need to be secured

Proposal: Delay notation rc.1 release for 2 weeks, the new date is `Nov 28`

## Detail
Part I: Cost for pure refactoring

* cost for refactoring notation-go
    * Implementation (`2 weeks` with UT, by Nov 15)
    * PR review ()
* cost for notation CLI using new notation-go APIs
    * implementation (`1 week`, no E2E test)
        * Can only start after notation-go refactoring is done, so the earliest date is by Nov 22

Part II: The impact of refactoring
* Save costs for the following issues
    * rc.1 issue [support `--debug` option](https://github.com/notaryproject/notation/issues/300)
        * implementation (Cost reduced from 2 weeks to `0.4 week`)
        * PR review ()
    * rc.1 issue [Using Verifier without a repository](https://github.com/notaryproject/notation-go/issues/143)
        * Cost reduced from 1 week to 0, covered by refactoring
    * rc.1 issue [System vs User file/directory precedence](https://github.com/notaryproject/notation/issues/203)
        * covered by refactoring
        * Remove code for system directy but keep the extensibility for future implementation
* New issues fixed by refactoring
    * Signing workflow is not fully compliant with spec

Part III: Other rc.1 issues owned by MSFT
* OCI artrifact support (high priority), covered by refactoring
    * only E2E testing needed after refactoring
* [User Story] - Notation sign/verify Tag to Digest translation (high priority)
    * cost: `0.6 week`
* E2E testing framework (medium priority)
    *  need improvement based on ORAS E2E solution
* * Notation list pagination (low priroity)
    * Suggest to move to future  
