Conversation on this thread are limited to 0.58.6 release's 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.6 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.58-stable branch yourself, in order to ensure that the process proceeds smoothly.
In this particular scenario, we actually won't publish a 0.58.7 release unless major issues appear: we are getting close to the 0.59.0 stable status so we prefer to focus on that - you can keep up to date about it here.
Conversation on this thread are limited to 0.58.6 release's 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.6 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.58-stable branch yourself, in order to ensure that the process proceeds smoothly.
In this particular scenario, we actually won't publish a 0.58.7 release unless major issues appear: we are getting close to the 0.59.0 stable status so we prefer to focus on that - you can keep up to date about it here.