David Tesar

Agree with Samir's three bullets. expiry wouldn't really change as it is just a user-defined timestamp. As far as `--push-reference` I'd also agree to remove. With cache - we should...

Sorry - the HOL steps needs to be updated to point to this path: https://github.com/Microsoft/PartsUnlimitedMRPmicro/blob/master/OrderSrvc/Dockerfile So the build definition should be: `$(Agent.BuildDirectory)/s/OrderSrvc/Dockerfile` Can you try that out and confirm it...

@iamsamirzon @SteveLasker @FeynmanZhou @yizha1 I propose we close roadmap issues like this one and these below since the roadmap repo should be covering this. This notaryproject repo can be for...

I agree there is some value in extracting the missing ideas/features from the 1-3 items into the roadmap repo. As you mentioned Samir, some of the things have been implemented...

Docker extension for notary is an option. There was a [POC here](https://github.com/notaryproject/notation/pull/269), but wanted to remove it since it wasn't currently under active development.

On the community call today, there are several places where this is in the documents which need consolidation. Also the https://github.com/notaryproject/notaryproject/blob/main/key-revocation.md seems like it should be more of certificate revocation,...

@SteveLasker - does this issue still make sense to keep considering we have the e2e scenario with ratify?

I think what @SteveLasker is getting at is the design spec on how `notation cert add` interacts with the config / trust stores / policies. I don't see any relevant...

I don't think it needs to be present for RC-1 as long as the usability is reasonable. I just don't think we should close this item out yet as I...

What Steve is referring to here though is the core plugin capability being available for `notation cert generate`. Agree the code to get the cert from the plugin provider should...