List view
- No due date•11/11 issues closed
- Due by April 29, 2024•15/15 issues closed
Issues with this label describe feature work or bugs that will not be worked on by the React Native Windows team in the future. The issues remain open to track the feature work or bug in case other developers try to file a similar issue.
No due date•40/40 issues closed- Due by December 11, 2023•57/57 issues closed
- Due by June 23, 2023•27/27 issues closed
- Due by January 23, 2023•42/42 issues closed
- No due date•20/20 issues closed
[First Preview](https://github.com/microsoft/react-native-windows/releases/tag/react-native-windows_v0.69.0-preview.1) available May 5, 2022
Due by June 30, 2022•42/42 issues closed- Due by April 4, 2022•44/44 issues closed
- Due by January 24, 2022•43/43 issues closed
- Due by October 18, 2021•67/67 issues closed
- Due by August 23, 2021•101/101 issues closed
- Due by March 12, 2021•117/117 issues closed
Update react-native-windows to match react-native's 0.62 (e.g. [v0.62.0-rc.0](https://github.com/facebook/react-native/releases/tag/v0.62.0-rc.0) or newer)
Due by May 29, 2020•143/143 issues closedUpdating react-native-windows to include [0.63](https://github.com/facebook/react-native/releases/tag/v0.63.0) from core
Due by August 31, 2020•105/105 issues closedThis "MVP" milestone tracks implementation of as much of RN core without significant workarounds current XAML (which would require [WinUI 3](https://github.com/microsoft/microsoft-ui-xaml/blob/master/docs/roadmap.md#winui-3)). - vNext is the default template (with vCurrent available as a fallback for compat for existing apps) - Native Modules ready to be developed - Measured percentage of lean core API completion (specific target percentage TBD) - Built on [WinUI 2.x](https://github.com/microsoft/microsoft-ui-xaml/)
Due by January 31, 2020•77/77 issues closedThis milestone tracks work items towards the next big update for react-native-windows @vnext. The broad themes for this milestone include: - Feature parity with RN 0.59 APIs - Native extensions APIs and developer experience for C++ & C# - Completion of mouse hover behaviors, XYFocus, Accessibility APIs started in Milestone 2. - Performance improvements - Test infrastructure and reliability
Due by October 30, 2019•142/142 issues closedUpdate: Extended due date by 2 weeks to complete some in progress items. Tracking the work to get vNext react-native-windows package to have key initial scenarios enabled. Goal: Developers can begin to create meaningful ReactNative apps for Windows 10 with adequate performance, accessibility and feature parity with React Native to unblock some of the key initial scenarios.
Due by July 12, 2019•60/60 issues closedTracking the first phase of RNWCPP to get adequately stood up. Goal: Customers can begin creating a new React Native app for Windows 10 using a simple CLI.
Due by April 15, 2019•22/22 issues closed- No due date•2/2 issues closed
Anything related to doc comments, README files, and the GitHub pages for React Native APIs.
No due date•12/12 issues closedGet a minimal UIExplorerApp working end-to-end on Windows.
Due by March 31, 2016•10/10 issues closed- No due date•24/24 issues closed
This milestone covers any work items that involve the React Native CLI; improved base classes for events, view managers, animation, native modules, etc,; and any other tools that may be useful for bootstrapping the React Native app creation and module sharing experience.
No due date•74/74 issues closed- No due date•5/5 issues closed
- No due date•1/1 issues closed
- No due date•105/105 issues closed
- No due date•54/54 issues closed
- No due date•16/16 issues closed
- No due date•28/28 issues closed