0.61.2 Discussion

[grabbou]

Conversations on this thread are limited to 0.61 releases major issues and backport (cherry-pick) requests from commits that are already on master.

An example of a good such request is a bug fix for a serious issue that has been merged into master but did not make the 0.61.2 cut.

In other words, if you cannot point to a particular commit on master, then your request likely belongs as a new issue in http://github.com/facebook/react-native/issues.

[grabbou]

Thanks for the requests. I was busy working on the CLI and trying to cut 0.62. in the meantime. I will look into your cherry-pick requests now.

[grabbou]

Following up on #148 (comment), I haven't had luck finding a root cause for the Android test failure. I am going to exclude it from this release.

Meanwhile, @radko93 (since you requested it), do have any ideas why this might be happening? I would appreciate your support on that and I am happy to revisit once this is working.

[grabbou]

Just finished cherry-picking and tests are on the CI. I had to cherry-pick few more ScrollView related commits in order to merge clearly the requests. Will look in few hours for the CI results and if all goes well, ship it.

[grabbou]

Releasing 0.61.3 now.

[grabbou]

I am going to revert a few additional commits.

• facebook/react-native@db662af - it fixes regression introduced in facebook/react-native@69c38e5, which isn't part of 0.61-stable
• facebook/react-native@0da6a9b - it fixes regression introduced in facebook/react-native@09c4e7c, which isn't part of 0.61-stable
• facebook/react-native@66ae1ca, breaks tests and no clear reason why it should be cherry-picked

Please, only request commits for fixes that you have experienced yourself using the release. We are keeping the cherry-picks for critical, blocking issues that happen to you while developing.

Suggesting commits that are fixing something that is not present in this release are slowing down the release process and require cherry-picking additional number of changes (e.g. in case of the two above commits, the original feature commit that introduced the bug).

You can see the history of the branch here: https://github.com/facebook/react-native/commits/0.61-stable

[grabbou]

For reference, here's the list of commits that is going to go with 0.61.3:

• facebook/react-native@2ddb76a
• facebook/react-native@2027a61
• facebook/react-native@5051bf2
• facebook/react-native@32c90eb
• facebook/react-native@766f470