0.58.x Discussion

[grabbou]

Conversation on this thread are limited to 0.58 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.58 RC 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]

Making this issue as a placeholder for upcoming 0.58.x release candidate. Going to cut a new release once 0.57 goes stable (which should happen later today). We can now all go and watch WWDC in the meantime.

[aaronschubert0]

Would be good to cherry pick react/react-native@22cf5dc to match the iOS support already in place for text transform.

[kelset]

We haven't cut 0.58 yet, so everything that you see on master at the moment will be in the 0.58 branch.

[aaronschubert0]

@kelset Ah awesome, sorry about that, thanks for clarifying 👍

[kelset]

NP - as a rough estimate, we'll probably try to first get a 0.57.1 up & running and then cut 0.58.

[grabbou]

If there's nothing major holding us from doing it now, I think we can cut it on Friday and release by Monday. That shouldn't interfere with Facebook window, unless someone's working over the weekend.

…

On Tue, 18 Sep 2018 at 17:29 Lorenzo Sciandra ***@***.***> wrote: NP - as a rough estimate, we'll probably try to first get a 0.57.1 up & running and then cut 0.58. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#41 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACWcxtiy8azHG1rqLCacQfoESp808pYMks5ucRE-gaJpZM4WlO4g> .

[kelset]

Quick update: after some conversation with the Core and the internal FB team, we decided to delay the cut and release of 0.58.x until the JSI feature lands into master - this also allow us to treat 0.57.x as as more "long term support" release (for, probably, at least another month) so that most developers will have time to update to it without the anxiety of having to do yet another upgrade right after.

[pvinis]

that would be nice, but in that case the xcode 10 issue should come to 0.57.x soon, even if its parts of it. ill check the other discussion in the other issue.

[xzilja]

Any chance to merge this and include in next release? react/react-native#18187

This enables react-native-svg to be animated on a native thread.

[rafaellincoln]

@kelset Is there any place where we can follow the discussion about JSI?

• What will she bring in benefits?
• Can problems occur when updating the RN?

[kelset]

@iljadaderko please limit the conversation to commits already on master.

@rafaellincoln there are a couple issues in the dedicated discussion repo (react-native-community/discussions-and-proposals#7 and react-native-community/discussions-and-proposals#11), and I'm sure that after it lands, some more content will be produced to explain more.

[EdwardDrapkin]

Will the flow upgrade (to 0.85) make it into 0.58?

[kelset]

@EdwardDrapkin yes. Since JSI landed, we are just waiting for the React sync to 16.6.0 commit to land and then we'll cut the first RC for 0.58.

So basically everything you see on master right now will be on that rc.