Remove exact versions from blog post #1447
Merged
Conversation
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
gaearon
commented
Nov 30, 2018
| @@ -32,7 +34,7 @@ We have a single vision for how all of these features fit together, but we're re | |||
|
|
|||
| The gradual release strategy helps us refine the APIs, but the transitional period when some things aren't ready can be confusing. Let's look at what these different features mean for your app, how they relate to each other, and when you can expect to start learning and using them. | |||
|
|
|||
| ### [React 16.6](/blog/2018/10/23/react-v-16-6.html): Suspense for Code Splitting (shipped) | |||
| ### [React 16.6](/blog/2018/10/23/react-v-16-6.html) (shipped): The One with Suspense for Code Splitting | |||
There was a problem hiding this comment.
This would have a nicer ring to it if we dropped "Suspense for". :-) But I want to emphasize the staggered rollout.
|
Deploy preview for reactjs ready! Built with commit 2207347 |
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.
The problem with using exact versions, as pointed out by @sebmarkbage, is that this doesn't let us release minors in the middle. It is very likely we'll need more minors in the middle so let's leave some wiggle room.
I figured this might as well introduce a naming convention for our releases? :-)