Repository navigation
Conversation
## Motivation and Context VERSIONING.md still opens its policy with a "Current 0.x Phase" section, written when the gem was below 1.0.0, and an "After 1.0.0" section describing the present as the future. The gem has been at 1.x since 1.0.0 shipped, so the two sections are replaced by the current rule, stated once: breaking changes ship only in major releases, with the exceptions the document goes on to describe, and the 0.x releases are mentioned as history. ## How Has This Been Tested? Docs only. ## Breaking Changes None.
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
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.
Motivation and Context
VERSIONING.md still opens its policy with a "Current 0.x Phase" section, written when the gem was below 1.0.0, and an "After 1.0.0" section describing the present as the future. The gem has been at 1.x since 1.0.0 shipped, so the two sections are replaced by the current rule, stated once: breaking changes ship only in major releases, with the exceptions the document goes on to describe, and the 0.x releases are mentioned as history.
How Has This Been Tested?
Docs only.
Breaking Changes
None.
Types of changes
Checklist