-
Notifications
You must be signed in to change notification settings - Fork 404
0.59.5 Discussion #118
Comments
This comment has been minimized.
This comment has been minimized.
It's been already requested, please look at my answer here: #113 (comment) |
I am going to cherry-pick React sync commit and do another release, as agreed yesterday. I now got confirmation from the Facebook team that there shouldn't be any problems. I will consider it "working" when all tests pass. |
React sync commit caused regressions that we didn't spot during testing. Note to self: Never cherry-pick React syncs, especially the ones that just landed, as they can cause some issues in production. 0.60.0-rc.0 will be out shortly and that should give you a place to test it. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
If there's no compatibility problems, this one would also be great to reduce bundle size. We already do this with a patch on top of RN. |
This is a simple change that fixes several build warnings that have started to appear in Xcode 10.2, particularly when using CocoaPods. It would be great if it could be included in the upcoming version. |
Please cherry pick
|
Please cherry pick:
|
Please cherry pick - thanks! [Android] [Fixed] - The ReactCookieJarContainer/ForwardingCookieHandler now handles the missing WebView gracefully. #24533 |
It should fix |
|
It would be nice if this one could get cherry picked: facebook/react-native@6f6696f [Android] [Fixed] - JS errors during bundle load were reported as UnknownCppException. (pull request facebook/react-native#24648) |
Cherry-picked everything except for @matthargett commits (yet to go through them and do it) and @Bardiamist (unfortunately, it doesn't merge clearly). I'll resume tomorrow morning. Note: The reason it took so long to get to cherry-picking commits to 0.59 was that we were working hard on 0.60. Now that we are partially on hold there, we are back here! |
There were some discussions happening yesterday regarding what we should still cherry pick before releasing this version. I am waiting to confirm the results of this conversation (timezone differences) and will be back to the release work. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
hey everyone, expect a new patch release of RN 0.59 next week-ish. We are still discussing this side of the whole process but we'll keep you updated as we decisions are reached. |
This comment has been minimized.
This comment has been minimized.
@grabbou is safe React Sync for cherry-pick? |
@matthargett, I didn't cherry-pick the following:
I am happy to discuss this for next patch release if you really need them. @ahce - React sync cannot be cherry-picked. |
Fixed haste for all out of tree platforms |
@matthargett - that one has been cherry-picked. I am now waiting for changelog and this is good to go. |
@grabbou Is there a reason why the above mentioned bugfix [Android] [Fixed] - LayoutAnimations cause invalid view operations facebook/react-native@20b4879 was not cherry picked? |
The commit didn't cherry-pick w/o issues - it has conflicts. Let me move it to 0.59.7 discussion issue and we will do another release. |
Closing in favour of #124 |
The release hasn't been cut yet due to Detox failure - we are investigating it. |
Conversation on this thread are limited to 0.59.5 release's major issues and 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.59.5 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.
If the commit you request to cherry pick is a complicated port, you will be asked to create the PR to the 0.59-stable branch yourself, in order to ensure that the process proceeds smoothly.
The text was updated successfully, but these errors were encountered: