-
Notifications
You must be signed in to change notification settings - Fork 231
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
editorial: Separate producer from platform requirements in Levels #1009
editorial: Separate producer from platform requirements in Levels #1009
Conversation
✅ Deploy Preview for slsa ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
cc @joshuagl since I added this to the v1.1 directory (please let me know, if this shouldn't be part of those changes) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like the clarity this separation of responsibilities brings!
1699223
to
5a2e52f
Compare
5a2e52f
to
07e9d3a
Compare
Signed-off-by: Marcela Melara <[email protected]>
Signed-off-by: Marcela Melara <[email protected]>
Co-authored-by: Andrew McNamara <[email protected]> Signed-off-by: Marcela Melara <[email protected]>
e973f1e
to
5feb8e3
Compare
Signed-off-by: Marcela Melara <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like how this has turned out, thanks Marcela and all the reviewers for iterating on this!
Co-authored-by: Joshua Lock <[email protected]> Signed-off-by: Marcela Melara <[email protected]>
The last set of recommended changes are in. Thank you all for the feedback! |
This PR adds a separate "Build Platform Requirements" row in each table of levels.md, more clearly defining what SW producers vs. build platform are responsible for at each level. To be clear, the requirements themselves have not changed, but rather the row in which they appear.
This change more closely matches the current separation in requirements.md, and also facilitates adding requirements for each role in higher/newer Build Track levels.