Skip to content
This repository has been archived by the owner on Jun 17, 2022. It is now read-only.

v0.64.0 Discussion #207

Closed
12 of 17 tasks
elicwhite opened this issue Aug 19, 2020 · 85 comments
Closed
12 of 17 tasks

v0.64.0 Discussion #207

elicwhite opened this issue Aug 19, 2020 · 85 comments

Comments

@elicwhite
Copy link
Contributor

elicwhite commented Aug 19, 2020

This release has not happened yet. This issue is for us to start tracking remaining work and coordinating with our relevant partner teams around the timing of the release

Highlighted Changes

Work Required

Hopeful Dates

We can never commit to the dates involved in a release as many things are out of our control. However, we are thinking about these rough dates for this release.

  • Cut the release branch: November 2nd-ish
  • Publish as Stable: November 9th-ish
@elicwhite elicwhite added stable Stable version backport request Cherry picking a change into an existing release labels Aug 19, 2020
@grabbou
Copy link
Member

grabbou commented Aug 19, 2020

Thank you! 🙏 I am about to get a deep dive into the CLI and prepare it for the next release. Will be back here with some features/updates/insights as that happens later this week.

@rachelnabors
Copy link

I want to thank @Simek for volunteering to handle updating the documentation with this release. Updating the API references at the start of the year increased learner satisfaction with the documentation by 70% (woohoo!).But they're very easy to let slide release over release! Until we have found a solid automation solution, it will be up to us to be meticulous and vigilant and keep them up to date with every release :)

@Simek
Copy link
Member

Simek commented Aug 20, 2020

The stub project for the docs release is here: https://github.com/facebook/react-native-website/projects/1

I have only skimmed over the changeset draft from this repository #205. I'm waiting for the official changelog in this thread, to start posting issues and implementing the necessary changes.

@gedeagas

This comment has been minimized.

@elicwhite

This comment has been minimized.

@thymikee

This comment has been minimized.

@elicwhite

This comment has been minimized.

@saphal1998
Copy link

saphal1998 commented Sep 13, 2020

@Simek, I'm also dropping a reference to the react-native-website PR here. I think it can be useful while writing docs for this release.

@mrousavy
Copy link
Member

  • Hermes with Proxy support (will now support react-native-firebase)

What exactly does that mean?

@Bardiamist
Copy link
Contributor

@mrousavy Now Hermes don't support js Proxy. So you can't use some packages from react-native-firebase which using Proxy.

@mikehardy
Copy link

  • Hermes with Proxy support (will now support react-native-firebase)

What exactly does that mean?

@mrousavy / @Bardiamist

👋 react-native-firebase maintainer here :-), it is our understanding that our package @react-native-firebase/database did not work with Hermes until recently as it required Proxy support. If Hermes supports Proxy now, then the last "not-Hermes-compatible" module for react-native-firebase should work. Success reports welcome of course (we have a few already)

Not sure if this is worth a by-name callout in the release notes or not (not my domain...) but those are the facts as I know them

Cheers

@grabbou

This comment has been minimized.

@Simek

This comment has been minimized.

@grabbou

This comment has been minimized.

@elicwhite

This comment has been minimized.

@viniciusfont

This comment has been minimized.

@mikehardy

This comment has been minimized.

@kelset

This comment has been minimized.

@rosskhanas

This comment has been minimized.

@kelset

This comment has been minimized.

@aleffita

This comment has been minimized.

@kelset

This comment has been minimized.

@grabbou

This comment has been minimized.

@kelset kelset removed backport request Cherry picking a change into an existing release stable Stable version labels Oct 21, 2020
@alloy

This comment has been minimized.

@thymikee

This comment has been minimized.

@kelset

This comment has been minimized.

@thymikee

This comment has been minimized.

@kelset

This comment has been minimized.

@thymikee

This comment has been minimized.

@grabbou

This comment has been minimized.

@alloy

This comment has been minimized.

@grabbou

This comment has been minimized.

facebook-github-bot pushed a commit to facebook/react-native that referenced this issue Nov 20, 2020
Summary:
Part of react-native-community/releases#207

Migrate warnings in index.js to point to new lean core repos

NOTE: some npm modules has been transferred to new nom namespace, such as `react-native-picker/picker` `react-native-async-storage/async-storage` `react-native-masked-view/masked-view`.
Some lean core repo has been transferred to new repo, but its npm namespace remains the same. ex: clipboard module exists in react-native-clipboard/clipboard repo, but npm package name is still `react-native-community/clipboard` (they're planned to be migrated in the future)

## Changelog

<!-- Help reviewers and the release process by writing your own changelog entry. For an example, see:
https://github.com/facebook/react-native/wiki/Changelog
-->

[General] [Changed] - Migrate warnings in index.js to point to new lean core repos

Pull Request resolved: #30422

Test Plan:
- Updated repo URL can be accessed
- Updated npm package can be installed

Reviewed By: rickhanlonii

Differential Revision: D25077750

Pulled By: cpojer

fbshipit-source-id: b736ea449835bdf3d2a2f85e5c86e5253b90db78
@brunolemos

This comment has been minimized.

@alloy

This comment has been minimized.

@grabbou

This comment has been minimized.

@kelset

This comment has been minimized.

@kelset

This comment has been minimized.

@brunolemos

This comment has been minimized.

@kelset

This comment has been minimized.

@grabbou

This comment has been minimized.

@grabbou

This comment has been minimized.

grabbou pushed a commit to facebook/react-native that referenced this issue Nov 23, 2020
Summary:
Part of react-native-community/releases#207

Migrate warnings in index.js to point to new lean core repos

NOTE: some npm modules has been transferred to new nom namespace, such as `react-native-picker/picker` `react-native-async-storage/async-storage` `react-native-masked-view/masked-view`.
Some lean core repo has been transferred to new repo, but its npm namespace remains the same. ex: clipboard module exists in react-native-clipboard/clipboard repo, but npm package name is still `react-native-community/clipboard` (they're planned to be migrated in the future)

## Changelog

<!-- Help reviewers and the release process by writing your own changelog entry. For an example, see:
https://github.com/facebook/react-native/wiki/Changelog
-->

[General] [Changed] - Migrate warnings in index.js to point to new lean core repos

Pull Request resolved: #30422

Test Plan:
- Updated repo URL can be accessed
- Updated npm package can be installed

Reviewed By: rickhanlonii

Differential Revision: D25077750

Pulled By: cpojer

fbshipit-source-id: b736ea449835bdf3d2a2f85e5c86e5253b90db78
@grabbou

This comment has been minimized.

@grabbou
Copy link
Member

grabbou commented Nov 23, 2020

I can confirm that a fresh new app works just fine on iOS with and without Hermes.

@alloy
Copy link
Member

alloy commented Nov 23, 2020

I can confirm that a fresh new app works just fine on Android with and without Hermes.

@grabbou
Copy link
Member

grabbou commented Nov 23, 2020

Closing and moving this to #214 as this issue is a bit long already.

@grabbou grabbou closed this as completed Nov 23, 2020
@react-native-community react-native-community locked as resolved and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests