rAF batching isn't supported and won't go in the docs, but batchedUpdates should.

is rAF batching discouraged, or just not suitable for shipping with core?

Would it be reasonable to link to an up-to-date npm project on the batchedUpdates page?

We don't use it at Facebook and it's not clear that it solves real problems, so we don't want to maintain it or have to fix bugs related to it. React.addons.batchedUpdates should give enough control over batching.

There are also known issues with rAF batching (mostly around controlled components).

Should we deprecate and eventually remove the RAF batching?

It's never been supported in any fashion.

(i.e., it's already deprecated?)

shouldn't this file be deleted in that case?
https://github.com/facebook/react/blob/master/src/addons/ReactRAFBatchingStrategy.js

That's not exposed as a public API in any of our builds, but sure, we can delete it – PR incoming.

Killed in #6016

We should document ReactDOM.unstable_batchedUpdates.

@spicyj Since when did we start documenting unstable_ features? Haven't we always left them intentionally undocumented? We also have unstable_renderSubtree and unstable_handleError and others, but I thought the decision was to not document them until they become stable. We document them as part of the release process.

It was a different situation when it was an addon, the issue made sense at that time.

Sure.