Blog post for 15.6.0 #9950

flarnie · 2017-06-13T18:42:17Z

what is the change?:
A short and sweet summary of 15.6.0 changes

why make this change?:
To thank community contributors and call out important changes.

test plan:
Visual inspection.
I also looked it over in a markdown viewer - http://dillinger.io/

issue:
#9398

**what is the change?:** A short and sweet summary of 15.6.0 changes **why make this change?:** To thank community contributors and call out important changes. **test plan:** Visual inspection. I also looked it over in a markdown viewer - http://dillinger.io/ **issue:** facebook#9398

flarnie · 2017-06-13T18:44:06Z

just noticed I need to add the customary 'Installation' and 'changelog' sections. Will do that now.

**what is the change?:** Added the 'Installation' section we have on most release blog posts, customized for the 15.6.0 version of React. Added the 'Changelog' from master to the blog post. **why make this change?:** To show folks how to install React and what changes are in this release. **test plan:** Visual inspection **issue:** facebook#9398

gaearon · 2017-06-13T19:39:24Z

docs/_posts/2017-06-13-react-v15.6.0.md

+---
+title: "React v15.6.0"
+author: flarnie
+---


I think you'll need to add yourself to https://github.com/facebook/react/blob/master/docs/_data/authors.yml for this to become a link.

gaearon

Let's remove this for now? I'll add when addons are bumped. Otherwise it's a bit misleading.

gaearon · 2017-06-13T19:45:28Z

Ugh GitHub interface confused me. Last comment refers to "React addons" section.

bvaughn · 2017-06-13T19:48:16Z

docs/_posts/2017-06-13-react-v15.6.0.md

+
+We recommend using a bundler like [webpack](https://webpack.js.org/) or [Browserify](http://browserify.org/) so you can write modular code and bundle it together into small packages to optimize load time.
+
+Remember that by default, React runs extra checks and provides helpful warnings in development mode. When deploying your app, make sure to [compile it in production mode](/react/docs/installation.html#development-and-production-versions).


I think this link no longer exists?
Should we instead link to https://facebook.github.io/react/docs/optimizing-performance.html#use-the-production-build

Yeah, we should! Good catch.

Thanks - so maybe we can change it to this:

When deploying your app, make sure to [use the production build](...link to that doc).

That works too.

gaearon

Accepted with changes requested above:

Add yourself to contributors so your name turns into a link
Use backticks for code-ish things
Second header should be ##, not #
Let's change production mode link to the new address per @bvaughn's comment
Need to update changelog with fixes from my PR

Otherwise looks great!

gaearon · 2017-06-13T20:00:28Z

docs/_posts/2017-06-13-react-v15.6.0.md

+We've also published version `15.6.0` of `react` and `react-dom` on npm, and the `react` package on bower.
+
+---
+


Let's roll the updates from #9951 here too.

Thanks! Will fix.

gaearon · 2017-06-13T20:01:20Z

docs/_posts/2017-06-13-react-v15.6.0.md

+
+Thanks to [Jason Quense](https://github.com/jquense) and everyone who helped out on those issues and PRs.
+
+# Downgrading Deprecation Warnings


I think this should start with ##. It looks giant compared to other headings otherwise.

gaearon · 2017-06-13T20:01:46Z

docs/_posts/2017-06-13-react-v15.6.0.md

+
+## Improving Inputs
+
+In React 15.6.0 the 'onChange' event for inputs is a little bit more reliable and handles more edge cases, including the following:


Let's use backticks, not apostrophes. Backticks appear as code blocks in the post.

gaearon · 2017-06-13T20:02:34Z

docs/_posts/2017-06-13-react-v15.6.0.md

+
+We are also including a couple of new warnings for upcoming deprecations. These should not affect most users, and for more details see the changelog below.
+
+After the last release, we got valuable community feedback that deprecation warnings were causing noise and failing tests. **In React 15.6, we have downgraded deprecation warnings to use 'console.warn' instead of 'console.error'.** Our other warnings will still use 'console.error' because they surface urgent issues which could lead to bugs. Unlike our other warnings, deprecation warnings can be fixed over time and won't cause problems in your app if shipped. We believe that downgrading the urgency of deprecation warnings will make your next update easier. Thanks to everyone who was involved in the discussion of this change.


Here, too, we should use backticks.

@bvaughn

**what is the change?:** - Add self to contributors so my name turns into a link - Use backticks for code-ish things - Second header to ##, not # - Change production mode link to the new address per @bvaughn's comment - Update changelog with fixes from facebook#9951 **why make this change?:** Make things more clear and accurate. **test plan:** Visual inspect - @flarnie will paste an image of how it appears in the actual docs. **issue:** facebook#9398

gaearon · 2017-06-13T21:56:42Z

docs/_posts/2017-06-13-react-v15.6.0.md

+In React 15.6.0 the `onChange` event for inputs is a little bit more reliable and handles more edge cases, including the following:
+
+* not firing when radio button is clicked but not changed ([issue 1471](https://github.com/facebook/react/issues/1471))
+* changing an input of type 'range' with the arrow keys ([issue 554](https://github.com/facebook/react/issues/554))


gaearon · 2017-06-13T21:59:03Z

docs/_posts/2017-06-13-react-v15.6.0.md

+
+Thanks to [Jason Quense](https://github.com/jquense) and everyone who helped out on those issues and PRs.
+
+## Downgrading Deprecation Warnings


Is "downgrading" universally understood in this context? Is there any equivalent way of saying it? "Softening Deprecation Warnings" or something like it. "Downgrading" sounds a bit related to versioning.

Agreed - not sure about 'Softening' either but will chat with folks and see what we come up with.

gaearon · 2017-06-13T22:00:38Z

docs/_posts/2017-06-13-react-v15.6.0.md

+
+We recommend using a bundler like [webpack](https://webpack.js.org/) or [Browserify](http://browserify.org/) so you can write modular code and bundle it together into small packages to optimize load time.
+
+Remember that by default, React runs extra checks and provides helpful warnings in development mode. When deploying your app, make sure to [use the production build](https://facebook.github.io/react/docs/optimizing-performance.html#use-the-production-build).


Generally we don't leave domain in posts in case we change the domain. So the link should start with /react/docs/... instead.

gaearon · 2017-06-13T22:05:47Z

docs/_posts/2017-06-13-react-v15.6.0.md

+
+In case you don't use a bundler, we also provide pre-built bundles in the npm packages which you can [include as script tags](/react/docs/installation.html#using-a-cdn) on your page:
+
+* **React**


If you leave two spaces after this line (and similar headers), you'll see newlines in rendered result.
Older posts have two spaces there.

Or you could use <br> to force it explicitly. (Two spaces after the line and <br> are equivalent in Markdown).

Nice!!! Thanks, will fix.

**what is the change?:** - Reword heading about deprecation warning changes - add 'br' s to the list of installation options - add some stray missing backticks **why make this change?:** Clarity and readability **test plan:** Visual inspection **issue:** facebook#9398

@bvaughn

* Blog post for 15.6.0 **what is the change?:** A short and sweet summary of 15.6.0 changes **why make this change?:** To thank community contributors and call out important changes. **test plan:** Visual inspection. I also looked it over in a markdown viewer - http://dillinger.io/ **issue:** #9398 * Add 'Installation' and 'Changelog' to 15.6.0 blog post **what is the change?:** Added the 'Installation' section we have on most release blog posts, customized for the 15.6.0 version of React. Added the 'Changelog' from master to the blog post. **why make this change?:** To show folks how to install React and what changes are in this release. **test plan:** Visual inspection **issue:** #9398 * Improvements to blog post, and add self to `authors.yml` **what is the change?:** - Add self to contributors so my name turns into a link - Use backticks for code-ish things - Second header to ##, not # - Change production mode link to the new address per @bvaughn's comment - Update changelog with fixes from #9951 **why make this change?:** Make things more clear and accurate. **test plan:** Visual inspect - @flarnie will paste an image of how it appears in the actual docs. **issue:** #9398 * Further improvements to 15.6 blog post **what is the change?:** - Reword heading about deprecation warning changes - add 'br' s to the list of installation options - add some stray missing backticks **why make this change?:** Clarity and readability **test plan:** Visual inspection **issue:** #9398

flarnie requested review from tomocchino, bvaughn and gaearon June 13, 2017 18:42

facebook-github-bot added the CLA Signed label Jun 13, 2017

gaearon reviewed Jun 13, 2017

View reviewed changes

bvaughn reviewed Jun 13, 2017

View reviewed changes

gaearon approved these changes Jun 13, 2017

View reviewed changes

gaearon reviewed Jun 13, 2017

View reviewed changes

flarnie merged commit ce6108d into facebook:master Jun 13, 2017

flarnie deleted the addBlogPostFor15.6Release branch May 25, 2018 17:52

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Blog post for 15.6.0 #9950

Blog post for 15.6.0 #9950

flarnie commented Jun 13, 2017 •

edited

flarnie commented Jun 13, 2017

gaearon Jun 13, 2017

gaearon left a comment

gaearon commented Jun 13, 2017

bvaughn Jun 13, 2017

gaearon Jun 13, 2017

flarnie Jun 13, 2017

gaearon Jun 13, 2017

gaearon left a comment

gaearon Jun 13, 2017

flarnie Jun 13, 2017

gaearon Jun 13, 2017

gaearon Jun 13, 2017

gaearon Jun 13, 2017

gaearon Jun 13, 2017

gaearon Jun 13, 2017

flarnie Jun 13, 2017

gaearon Jun 13, 2017

flarnie Jun 13, 2017

gaearon Jun 13, 2017

flarnie Jun 13, 2017


		We recommend using a bundler like [webpack](https://webpack.js.org/) or [Browserify](http://browserify.org/) so you can write modular code and bundle it together into small packages to optimize load time.

		Remember that by default, React runs extra checks and provides helpful warnings in development mode. When deploying your app, make sure to [compile it in production mode](/react/docs/installation.html#development-and-production-versions).

		We've also published version `15.6.0` of `react` and `react-dom` on npm, and the `react` package on bower.

		---


		Thanks to [Jason Quense](https://github.com/jquense) and everyone who helped out on those issues and PRs.

		# Downgrading Deprecation Warnings


		## Improving Inputs

		In React 15.6.0 the 'onChange' event for inputs is a little bit more reliable and handles more edge cases, including the following:


		We are also including a couple of new warnings for upcoming deprecations. These should not affect most users, and for more details see the changelog below.

		After the last release, we got valuable community feedback that deprecation warnings were causing noise and failing tests. In React 15.6, we have downgraded deprecation warnings to use 'console.warn' instead of 'console.error'. Our other warnings will still use 'console.error' because they surface urgent issues which could lead to bugs. Unlike our other warnings, deprecation warnings can be fixed over time and won't cause problems in your app if shipped. We believe that downgrading the urgency of deprecation warnings will make your next update easier. Thanks to everyone who was involved in the discussion of this change.


		Thanks to [Jason Quense](https://github.com/jquense) and everyone who helped out on those issues and PRs.

		## Downgrading Deprecation Warnings


		In case you don't use a bundler, we also provide pre-built bundles in the npm packages which you can [include as script tags](/react/docs/installation.html#using-a-cdn) on your page:

		* React

Blog post for 15.6.0 #9950

Blog post for 15.6.0 #9950

Conversation

flarnie commented Jun 13, 2017 • edited

flarnie commented Jun 13, 2017

Choose a reason for hiding this comment

gaearon left a comment

Choose a reason for hiding this comment

gaearon commented Jun 13, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

gaearon left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

flarnie commented Jun 13, 2017 •

edited