-
Notifications
You must be signed in to change notification settings - Fork 26
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
Spec clarifications #75
Conversation
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.
This set of changes look fine to me. I did not go through ITEs 1-5 carefully to ensure that they are all well integrated into this version of the spec. I believe that is necessary before this becomes the finalized 1.0 version...
Signed-off-by: Aditya Sirish <[email protected]>
d4d5ba3
to
cdc977a
Compare
Signed-off-by: Aditya Sirish <[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.
Left a few comments but they aren't blockers.
Signed-off-by: Aditya Sirish <[email protected]>
#45 may be a blocker. |
Blocker for 1.0, but not for this PR, right? |
6459156
to
852d368
Compare
Signed-off-by: Aditya Sirish <[email protected]>
852d368
to
7479530
Compare
I've updated the require rule bits as well and I think we've now clarified how it works. |
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.
Great improvements!
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.
Nice, this is quite tighter!
Shall we merge and tag RC? |
This PR includes more spec clarifications and some formatting changes. Highlights:
The PR also optimistically bumps the version to 1.0-RC!
Closes #45, #71, #72.