[0.27] Commits to cherry-pick into stable release

[grabbou]

0.27.0-rc1:

• Use React 15.1.0 and stop using the alpha 7d1b4d6
• Fix Chrome debugging on Android 24a806a
• Made npm deployment to be independent of git tags cache 934acd8
• Respect original enumerability/writability when polyfilling globals cacf6b1

0.27.0-rc2:

• Update node-haste dependency to 2.12.0 (for RN Windows) 68af89d

0.27.0-stable

• Fix CocoaPods spec 3ba232f

Commits cherry-picked so far:
https://github.com/facebook/react-native/commits/0.27-stable

[ide]

Summarizing the discussion about React from #7385:

• RN currently depends on an alpha release of react
• npm doesn't support prereleases very well
• The React team is aiming to publish a non-prerelease version of react to npm by Monday
• So we'll publish RN 0.27-rc now and mention the prerelease peerDep issue in Known Problems of the release notes
• And when react 15.1.0 is published, we'll update RN's package.json on the 0.27-stable branch and publish 0.27-rc.2

[grabbou]

Thanks @ide for the great summary. I am currently out of the office, but will do the release first thing tomorrow morning (in fact I've already cut it 2 days ago, so just need to update with latest stuff).

[bestander]

#7619 - makes publishing to npm a bit less flaky

[ide]

f7c4ed8, which fixes the Chrome debugger needs to be cherry picked.

I also already added a commit to 0.27-stable that makes us use React 15.1.0 instead of the alpha: 7d1b4d6

[grabbou]

I've cherry-picked all the mentioned commits + 3d8725d to make sure 0.27-rc also works well with Sentry. Doing manual e2e tests to make sure all works fine and sending it to npm.

@ide unfortunately the Chrome debugging still seems to be broken with the same exception, maybe we forgot to update the signature in other places. Anyway - I am shipping it as is to get the React fix and Sentry out faster.

[rozele]

Could we also cherry-pick 68af89d? It's another prereq for getting the react-native-windows NPM package out.

cc @mkonicek

[rozele]

@grabbou #7787, if it's not too late.

[grabbou]

I think we still have some time. I need to test the debugger because from my internal testing it wasn't working despite the fix being landed recently. It could've been my local gradle cache.

[grabbou]

@rozele was the #7787 PR cherry-picking 68af89d? If yes, I can just cherry-pick it directly and push to the branch.

[rozele]

@grabbou Yes. That would be great. I don't have push access anyway :-)

[mkonicek]

@grabbou I updated the description to make it easy to keep track of what's been cherry-picked. Reading the comments I can't tell for sure - the comments are more of a discussion.

[satya164]

Just a heads up, we should publish RCs as 0.27.0-rc.1 instead of 0.27.0-rc1 so that NPM picks up the patch releases.

[bestander]

Ah, magic.
I think our npm publish script will work fine with that.
Just need to update docs on the tag format

On Tuesday, 31 May 2016, Satyajit Sahoo notifications@github.com wrote:

Just a heads up, we should publish RCs as 0.27.0-rc.1 instead of
0.27.0-rc1 so that NPm picks up the patch releases.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#7616 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ACBdWMcLmT353Gqcqv2gIt2mGAXKiIQDks5qG-74gaJpZM4IhdZq
.

[bestander]

@satya164 , would you send a PR to change the docs?
Considering that you found this out

On Tuesday, 31 May 2016, Satyajit Sahoo notifications@github.com wrote:

Just a heads up, we should publish RCs as 0.27.0-rc.1 instead of
0.27.0-rc1 so that NPm picks up the patch releases.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#7616 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ACBdWMcLmT353Gqcqv2gIt2mGAXKiIQDks5qG-74gaJpZM4IhdZq
.