Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notary v2: RC1 #70

Open
SteveLasker opened this issue May 12, 2021 · 5 comments
Open

Notary v2: RC1 #70

SteveLasker opened this issue May 12, 2021 · 5 comments
Labels
Milestone

Comments

@SteveLasker
Copy link
Contributor

Notary V2 RC1 will be a time & quality-based release targeting the Fall of 2021.

Notary v2 RC1 will be dependent upon Artifacts RC1 (Reference Type Support)

Scope

The scope of RC1 is targeted to be complete by June 2021, providing time for a summer 2021 release and fall dependency for consumers.

@SteveLasker SteveLasker added this to the Notary v2: RC1 milestone May 12, 2021
@mnm678
Copy link
Contributor

mnm678 commented Jun 25, 2021

We need to update this milestone. The Notary project requirements and threat model are still under active development, so I don't think it's possible to have a release of an implementation of these requirements before the end of the year at the earliest.

@dtzar dtzar modified the milestones: Notary v2: RC1, RC-1 Jun 28, 2022
@dtzar
Copy link
Contributor

dtzar commented Aug 3, 2022

@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 proposed high-level spec/designs/scenarios before they are a user story notation* implements.

  1. Prototype 3 Scope DRAFT #52
  2. Artifacts: RC1 (Reference Type Support) #68
  3. Artifacts: RC2 (Versioned Artifact Support) #69

@FeynmanZhou
Copy link
Member

@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 proposed high-level spec/designs/scenarios before they are a user story notation* implements.

  1. Prototype 3 Scope DRAFT #52
  2. Artifacts: RC1 (Reference Type Support) #68
  3. Artifacts: RC2 (Versioned Artifact Support) #69

@dtzar Why not transfer these issues to the Roadmap repo? I think they are still under discussion.

@iamsamirzon
Copy link

@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 proposed high-level spec/designs/scenarios before they are a user story notation* implements.

  1. Prototype 3 Scope DRAFT #52
  2. Artifacts: RC1 (Reference Type Support) #68
  3. Artifacts: RC2 (Versioned Artifact Support) #69

@dtzar Why not transfer these issues to the Roadmap repo? I think they are still under discussion.

@dtzar - I am aligned with you to close these items highlighted above . But before we move them as is in the roadmap repo, lets see if these are still needed as is, or should we close them and create net new in roadmap repo with the desired feature. I believe we have already implemented these items.

@dtzar
Copy link
Contributor

dtzar commented Aug 5, 2022

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 or may not make sense at this time.

This particular issue we're commenting in I don't see any merit in.

I also don't like the idea of any "RC" milestone or dates being listed in the notaryproject repo. This repo should just be for future ideas/designs - pre-backlog.

We could also consider modifying the 1-3 issues there into more pure spec/design ideas (i.e. remove the RC/timelines and such) which still sense, then adding new user story(ies) on the roadmap repo and link to those.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants