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
Use consistent informative versioning scheme - Closes #2594 #2751
Merged
MaciejBaj
merged 34 commits into
development
from
2594_Use_consistent_informative_versioning_scheme
Jan 28, 2019
Merged
Use consistent informative versioning scheme - Closes #2594 #2751
MaciejBaj
merged 34 commits into
development
from
2594_Use_consistent_informative_versioning_scheme
Jan 28, 2019
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
…versions, such as leading zeros and < 1.0
MaciejBaj
changed the title
2594 use consistent informative versioning scheme - Closes #2594
Use consistent informative versioning scheme - Closes #2594
Jan 17, 2019
2snEM6
force-pushed
the
2594_Use_consistent_informative_versioning_scheme
branch
2 times, most recently
from
January 18, 2019 14:14
5ac2a26
to
cc7d1ee
Compare
2snEM6
force-pushed
the
2594_Use_consistent_informative_versioning_scheme
branch
from
January 18, 2019 14:16
cc7d1ee
to
95fa2ce
Compare
diego-G
suggested changes
Jan 18, 2019
db/sql/migrations/updates/20190111111557_add_protocolVersion_column_to_peers.sql
Outdated
Show resolved
Hide resolved
diego-G
reviewed
Jan 18, 2019
lsilvs
reviewed
Jan 21, 2019
db/sql/migrations/updates/20190111111557_add_protocolVersion_column_to_peers.sql
Outdated
Show resolved
Hide resolved
2snEM6
force-pushed
the
2594_Use_consistent_informative_versioning_scheme
branch
2 times, most recently
from
January 21, 2019 14:58
145e160
to
15978dc
Compare
2snEM6
force-pushed
the
2594_Use_consistent_informative_versioning_scheme
branch
from
January 21, 2019 15:58
15978dc
to
4f4687c
Compare
2snEM6
changed the base branch from
feature/extensible-data-persistence-model
to
development
January 24, 2019 08:44
diego-G
previously approved these changes
Jan 25, 2019
MaciejBaj
reviewed
Jan 25, 2019
MaciejBaj
approved these changes
Jan 28, 2019
MaciejBaj
deleted the
2594_Use_consistent_informative_versioning_scheme
branch
January 28, 2019 16:27
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.
What was the problem?
There was no separation of concerns between protocol changes and implementation changes in the current versioning scheme.
For further information, please refer to LIP0007.
How did I fix it?
By implementing LIP007.
Now nodes are aware of the protocol version other peers are running on and therefore they perform compatibility checks against this version.
How to test it?
npm test -- mocha:extensive:unit
npm test --mocha:extensive:functional
npm test -- mocha:default:network
Review checklist