-
Notifications
You must be signed in to change notification settings - Fork 404
0.57.2 Discussion #46
Comments
Current situation:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@ChrisEdson, @cristeahub thanks for the feedback on that but please let's try to keep the conv around commits and cherry picks ;) (the reason why my comment describes the situation is because I want to tunnel people that may end up in this issue to those links instead of writing stuff here ;D ) |
I want the following to be cherry-picked:
|
|
Thanks @radeno for the suggestions! Regarding FBJS I'd prefer to avoid it because it's not directly fixing anything AFAIK (and that package itself is, by self admission, not directly for OSS). A few more commits I want to see cherry picked:
|
@kelset you are right about FBJS. I don't like fix to http/https protocol. (facebook/react-native@d00bdb9) It is Android specific, but fix code appears on React Native side, not Android side. That commit smells. Android have from API v16 (which is minimal SDK for 0.57 right?) normalization method: https://developer.android.com/reference/android/net/Uri.html#normalizeScheme() Update: |
Yeah I agree with your assessment @radeno, go for it 👍 |
I don't claim to know the internal release workings of React, but is it wise for RN to be often syncing with their alpha versions? 16.6.0-alpha.400d197 in @kelset's linked PR. |
I share your concern of moving to an alpha dep, but considering that most likely there won't be another sync commit until after ReactConf (Oct 25th) IF testing goes well I'd prefer to allow people to be able to a update to a version of RN that allows them to use 16.5.2 (which is currently not the case). And we are not often using alpha versions. |
I'd like to get this commit picked to add a deprecation warning to ListView: facebook/react-native@e90f5fa |
Another fixes:
|
thanks for the links! I'm just waiting for this to land facebook/react-native#21570 (which I think it's simply a matter of some automated process to complete) and I'll proceed to cherry pick & test 💪 |
This comment has been minimized.
This comment has been minimized.
Yes, it's OT for this issue so I've opened via GitHub a dedicated issue, see #47 - we can discuss about it there. |
Going to cherry-pick them later in the afternoon. Will be updating this thread shortly. |
Let’s include the deprecation warning for ListView as well. |
@kelset Lorenzo , do i understand correctly, 57.3 will not have a fix for google build tools 3.2 or it will? Thank you |
@jeveloper even 0.58 doesn't have any support about new building system. It is still in progress facebook/react-native#21628 |
let's get these safe deprecation/warning commits in, as discussed on Slack: |
@matthargett, two of those commits were listed by other people earlier up. The third one doesn't seem relevant it is changing an RNTester file. Did you mean to link to something else instead? |
All commits from this comment, this and this one have been cherry-picked. Note: In order to cherry-pick Fix InterpolatorType crash on Android, I had to cherry-pick facebook/react-native@0df8e7d, facebook/react-native@69a51da and facebook/react-native@677f1de. |
(reopening temporarily until I fix the release of 0.57.3) |
@kelset these two commits missing: don't you want it in 0.57.3? |
@jeveloper there is already a workaround in 0.57.2 (so the version of RN currently available should be able to work with Android Studio 3.2) -> facebook/react-native@a4fed6e @radeno I didn't do the actual cherry-pick for release yesterday, probably it was overlooked. I'm fixing some CI issues atm, once everything is green again I'll try to get those in too. |
Ok, 0.57.3 is out. Headsup, you need to update react and test-renderer to |
Conversation on this thread are limited to 0.57.2 release's major issues and backport (cherry-pick) requests from commits that are already on master - so that we can then produce a 0.57.3 release in the near future.
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.57.1 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.
The text was updated successfully, but these errors were encountered: