Add "Version 0.1" to some md files in prep for release#170
Merged
duglin merged 1 commit intocloudevents:masterfrom Apr 20, 2018
Merged
Add "Version 0.1" to some md files in prep for release#170duglin merged 1 commit intocloudevents:masterfrom
duglin merged 1 commit intocloudevents:masterfrom
Conversation
Also added a "Status" section to be consistent across all 3 docs. This should address @inline's concern about people thinking anything is set in stone because now it says its a 'working draft'. Signed-off-by: Doug Davis <dug@us.ibm.com>
Contributor
|
LGTM |
Contributor
|
LGTM as-is. I would appreciate if we'd formalize spec editor status as in most other bodies of this sort and then reflect that in the docs. |
Collaborator
Author
|
Syntax/editorial changes in prep for v0.1 - got 2 LGTMs, merging. |
Contributor
|
LGTM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Also added a "Status" section to be consistent across all 3 docs.
This should address @inline's concern about people thinking anything
is set in stone because now it says its a 'working draft'.
One thing we need to decide, later, is whether to have section numbers or not, we not consistent right now.
Signed-off-by: Doug Davis dug@us.ibm.com