Add notes for April, 21 #8
Conversation
| * In six months, master and 15.x can diverge significantly. | ||
| * We need to figure out a better story around syncing React with: | ||
| * The Facebook website. | ||
| * React Native. |
There was a problem hiding this comment.
Is there any need to have a better story around syncing React with the outside community? Or is npm and the semver changes seen as sufficient for that front and only internal consumers needs to be tackled now?
There was a problem hiding this comment.
Can you explain in a little more detail what you mean by syncing externally?
At Facebook, we have a monorepo, and it is the source of truth for the website. So we literally copy the new files into the Facebook repo from master once a couple of weeks, catch regressions or find bugs in our own components, fix those, and then land the change. It can get reverted if something turns out to break in the internal testing, so this process is manual so we have full control over it and can cherry-pick commits if necessary. Generally, this syncing helps ensure that by the time we cut an open source release, the code is already in production so we don’t have big regressions. (Obviously this didn’t entirely pan out in 15.)
I’m not sure what would be an external equivalent of that.
Please use this pull request for the discussion!