You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
formalizing a versioning scheme and changelog policy
#218
non-breaking (e.g.: wording refinements and clarifications)
soft-breaking (e.g.: message field renaming, shuffling RFC2119 key words)
hard-breaking (e.g.: message field addition or removal)
meanwhile, projects like interoperability-tests-sv2 are driving changes such as #211 (and it's reasonable to expect more to come as the project matures)
on the other hand, we're getting to a point where people are actively using the protocol... which means that regardless of spec change severity, changes will always impact adopters to some capacity
so we should consider formalizing a versioning scheme, under the assumption that interoperable implementations will leverage versioning primitives established on SetupConnection.{min_version, max_version}
and along with that, each version bump should be followed by a changelog that becomes part of the protocol spec markdown files
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
spec change severity can be categorized as:
meanwhile, projects like
interoperability-tests-sv2are driving changes such as #211 (and it's reasonable to expect more to come as the project matures)on the other hand, we're getting to a point where people are actively using the protocol... which means that regardless of spec change severity, changes will always impact adopters to some capacity
so we should consider formalizing a versioning scheme, under the assumption that interoperable implementations will leverage versioning primitives established on
SetupConnection.{min_version, max_version}and along with that, each version bump should be followed by a changelog that becomes part of the protocol spec markdown files
All reactions