{"action":"closed","issue":{"url":"https://api.github.com/repos/facebook/react-native/issues/3291","labels_url":"https://api.github.com/repos/facebook/react-native/issues/3291/labels{/name}","comments_url":"https://api.github.com/repos/facebook/react-native/issues/3291/comments","events_url":"https://api.github.com/repos/facebook/react-native/issues/3291/events","html_url":"https://github.com/facebook/react-native/issues/3291","id":110533233,"number":3291,"title":"[0.13] Planning the next RC","user":{"login":"ide","id":379606,"avatar_url":"https://avatars.githubusercontent.com/u/379606?v=3","gravatar_id":"","url":"https://api.github.com/users/ide","html_url":"https://github.com/ide","followers_url":"https://api.github.com/users/ide/followers","following_url":"https://api.github.com/users/ide/following{/other_user}","gists_url":"https://api.github.com/users/ide/gists{/gist_id}","starred_url":"https://api.github.com/users/ide/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ide/subscriptions","organizations_url":"https://api.github.com/users/ide/orgs","repos_url":"https://api.github.com/users/ide/repos","events_url":"https://api.github.com/users/ide/events{/privacy}","received_events_url":"https://api.github.com/users/ide/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":14,"created_at":"2015-10-08T20:19:27Z","updated_at":"2015-10-13T22:18:04Z","closed_at":"2015-10-13T22:18:04Z","body":"@mkonicek is on 0.12 and we'll cut 0.13-rc soon after. Here are the main bugs that are holding up the release:\r\n\r\n**General**:\r\n- [x] ObjC tests are red - @javache looking into it, likely related to [this commit](https://github.com/facebook/react-native/commit/9e81dec5e44daf75f77a92635b75879dfa843990)\r\n- [x] E2E tests are red - https://github.com/facebook/react-native/issues/3304, pinged @martinbigio\r\n\r\n**iOS:**\r\n- [ ] 3D touch breaks the gesture system due to an iOS 9.0 bug we should handle (@nicklockwood and @tadeuzagallo looking): https://github.com/facebook/react-native/issues/3082\r\n\r\n**Android:**\r\n- [x] ReadableNativeArray is missing, cannot compile: https://github.com/facebook/react-native/issues/3276, @mikearmstrong001 is looking into it\r\n- [x] Reports that the Android UIExplorer has a redbox (need to verify on master but think I encountered this): https://github.com/facebook/react-native/issues/2983\r\n- [x] Example apps crashing on Android (needs verification): https://github.com/facebook/react-native/issues/3289\r\n\r\n**Infra:**\r\n- [x] Packager has a syntax error due to not being transformed in some cases: https://github.com/facebook/react-native/issues/3262, @martinbigio says fix coming soon\r\n- [ ] Test the basic workflow on Windows even if everything doesn't work like the Chrome debugger. After discussing with @mkonicek we're going to start with Windows support being a Community Responsibility and communicate that clearly. The best Windows support is going to come from people developing with RN master and using Windows on a daily basis so if someone wants to step up to the plate we can work with them on that. People are helping in #3348.\r\n- [x] Rudimentary npm 3 support. We should get things to work even if the state of npm 3 isn't great. I believe there's a huge perf regression (may be fixed!) so most core devs are sticking with npm 2 but if it's not too hard to get npm 3 to be useable let's do that. #3317\r\n\r\nIt would be nice if we could include the AAR/JAR files with the npm distribution but it's not a launch blocker. Perhaps we could do that for 0.13 or 0.14-rc.\r\n\r\nI'll take care of drafting the changelog."}}