status-im
/
react-native
mirror of https://github.com/status-im/react-native.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
react-native/blog/2017-01-07-monthly-release-...

37 lines
2.7 KiB
Markdown
Raw Normal View History

Blog post about new versions and release cadence Summary: This should be pretty self-explanatory Closes https://github.com/facebook/react-native/pull/11757 Differential Revision: D4392099 Pulled By: ericvicenti fbshipit-source-id: 81d54b11c7e3ce5dcdfb62b219e6bcec1f7e43ac
2017-01-09 09:05:25 +00:00
---
title: A Monthly Release Cadence: Releasing December and January RC
author: Eric Vicenti
authorTitle: Engineer at Facebook
authorURL: https://twitter.com/EricVicenti
authorImage: https://secure.gravatar.com/avatar/077ad5372b65567fe952a99f3b627048?s=128
authorTwitter: EricVicenti
category: announcements
---
Shortly after React Native was introduced, we started releasing every two weeks to help the community adopt new features, while keeping versions stable for production use. At Facebook we had to stabilize the codebase every two weeks for the release of our production iOS apps, so we decided to release the open source versions at the same pace. Now, many of the Facebook apps ship once per week, especially on Android. Because we ship from master weekly, we need to keep it quite stable. So the bi-weekly release cadence doesn't even benefit internal contributors anymore.
Some more Exponent -> Expo updates Summary: Updates the remaining references to Exponent to Expo, similar in spirit to b698b4ad62cee4673bcf404f533a49d76069d8da. Left the filename of the blog post alone so that permalinks keep working. Closes https://github.com/facebook/react-native/pull/12776 Differential Revision: D4676911 Pulled By: hramos fbshipit-source-id: 5b8b8413f95c984df4157e4e1634dd35a78afa29
2017-03-08 23:38:08 +00:00
We frequently hear feedback from the community that the release rate is hard to keep up with. Tools like [Expo](https://expo.io/) had to skip every other release in order to manage the rapid change in version. So it seems clear that the bi-weekly releases did not serve the community well.
Blog post about new versions and release cadence Summary: This should be pretty self-explanatory Closes https://github.com/facebook/react-native/pull/11757 Differential Revision: D4392099 Pulled By: ericvicenti fbshipit-source-id: 81d54b11c7e3ce5dcdfb62b219e6bcec1f7e43ac
2017-01-09 09:05:25 +00:00
### Now releasing monthly
We're happy to announce the new monthly release cadence, and the December 2016 release, `v0.40`, which has been stabilizing for all last month and is ready to adopt. (Just make sure to [update headers in your native modules on iOS](https://github.com/facebook/react-native/releases/tag/v0.40.0)).
Although it may vary a few days to avoid weekends or handle unforeseen issues, you can now expect a given release to be available on the first day of the month, and released on the last.
### Use the current month for the best support
The January release candidate is ready to try, and you can [see what's new here](https://github.com/facebook/react-native/releases/tag/v0.41.0-rc.0).
To see what changes are coming and provide better feedback to React Native contributors, always use the current month's release candidate when possible. By the time each version is released at the end of the month, the changes it contains will have been shipped in production Facebook apps for over two weeks.
Update HTTP -> HTTPS in links in the docs Summary: URLs were updated to use HTTPS protocol <!-- Thank you for sending the PR! We appreciate you spending the time to work on these changes. Help us understand your motivation by explaining why you decided to make this change. You can learn more about contributing to React Native here: http://facebook.github.io/react-native/docs/contributing.html Happy contributing! --> Improves security and privacy. I tested all urls to insure that the destination supported https. This is an update to Docs only. [ DOCS ] [ ENHANCEMENT ] -URLs were updated to use HTTPS protocol <!-- Help reviewers and the release process by writing your own release notes **INTERNAL and MINOR tagged notes will not be included in the next version's final release notes.** CATEGORY [----------] TYPE [ CLI ] [-------------] LOCATION [ DOCS ] [ BREAKING ] [-------------] [ GENERAL ] [ BUGFIX ] [-{Component}-] [ INTERNAL ] [ ENHANCEMENT ] [ {File} ] [ IOS ] [ FEATURE ] [ {Directory} ] |-----------| [ ANDROID ] [ MINOR ] [ {Framework} ] - | {Message} | [----------] [-------------] [-------------] |-----------| [CATEGORY] [TYPE] [LOCATION] - MESSAGE EXAMPLES: [IOS] [BREAKING] [FlatList] - Change a thing that breaks other things [ANDROID] [BUGFIX] [TextInput] - Did a thing to TextInput [CLI] [FEATURE] [local-cli/info/info.js] - CLI easier to do things with [DOCS] [BUGFIX] [GettingStarted.md] - Accidentally a thing/word [GENERAL] [ENHANCEMENT] [Yoga] - Added new yoga thing/position [INTERNAL] [FEATURE] [./scripts] - Added thing to script that nobody will see --> Closes https://github.com/facebook/react-native/pull/17332 Differential Revision: D6635123 Pulled By: hramos fbshipit-source-id: f1d8b1a5268eb27d55198dd3d8a2f0aab20c405e
2017-12-24 23:55:48 +00:00
You can easily upgrade your app with the new [react-native-git-upgrade](https://facebook.github.io/react-native/blog/2016/12/05/easier-upgrades.html) command:
Blog post about new versions and release cadence Summary: This should be pretty self-explanatory Closes https://github.com/facebook/react-native/pull/11757 Differential Revision: D4392099 Pulled By: ericvicenti fbshipit-source-id: 81d54b11c7e3ce5dcdfb62b219e6bcec1f7e43ac
2017-01-09 09:05:25 +00:00
```
npm install -g react-native-git-upgrade
react-native-git-upgrade 0.41.0-rc.0
```
We hope this simpler approach will make it easier for the community to keep track of changes in React Native, and to adopt new versions as quickly as possible!
(Thanks go to [Martin Konicek](https://github.com/mkonicek) for coming up with this plan and [Mike Grabowski](https://github.com/grabbou) for making it happen)