Remove version number in file name #26
Merged
Conversation
This file contains 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
Putting the version number in the file name is not future proof
|
I think there will be more documents in |
|
We could remove version numbers altogether. It's a bit confusing to have "Ethereum 2.0" and "Spec version 2.1". |
|
What about I think it best to not just be "spec" in the context of what will be a bunch of spec docs. It will also imply that we should put the shard chains spec in another doc. Will also start updating the readme to link to various docs |
|
A separate doc for the shards makes sense |
|
handling merge conflict then merging |
hwwhww
pushed a commit
that referenced
this pull request
Jul 23, 2020
hwwhww
pushed a commit
that referenced
this pull request
Jul 23, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Putting the version number in the file name is not future proof