-
Notifications
You must be signed in to change notification settings - Fork 35
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
chore: add additional document statuses #139
Conversation
c542d42
to
b5d363a
Compare
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.
overall looks good. made a few minor comments
31fa1ea
to
a296bf8
Compare
Co-authored-by: Daniel Dyla <[email protected]> Signed-off-by: Todd Baert <[email protected]>
a296bf8
to
e2629c1
Compare
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'm not sure the benefit of Mixed
, but it's not like it's a problem
Ya I was hesitant about Mixed. It's not really a meaningful status unto itself, but more of a TBH we can probably completely remove it. We can annotate sections with statuses, it just means you'll have navigate to them to see them. |
Is there going to be requirements or guidelines on how the promotion is determined? For example what is required to go from Experimental -> Hardening? |
@InTheCloudDan that's a good question. I think some kind of formality could be good. I'm not sure what that could be. I'll think about it 🤔 Anyone else have ideas for this? |
Signed-off-by: Todd Baert <[email protected]>
|
925f5f2
to
9fe8b79
Compare
Signed-off-by: Todd Baert <[email protected]>
9fe8b79
to
73e1ed6
Compare
Signed-off-by: Todd Baert <[email protected]>
Signed-off-by: Todd Baert <[email protected]>
Adds document statuses explaining stability of various spec documents and sub-sections.
This is important as we move toward's 1.0 SDK releases and a stable spec.