status-im/react-native
2
0
Fork 0
mirror of https://github.com/status-im/react-native.git synced 2025-01-13 19:15:05 +00:00
Code Issues Projects Releases Wiki Activity

Update releases to refer to month instead of two weeks

Browse Source 
Summary: We also have to update internal guides.

Differential Revision: D4265258

fbshipit-source-id: 72ee394138464f8145075b499b862561e7a2ed40
This commit is contained in:
Mike Grabowski 2016-12-02 04:52:57 -08:00 committed by Facebook Github Bot
parent 56fb3db693
commit 830d7f6426
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Releases.md
View File

@ -5,11 +5,10 @@ https://github.com/facebook/react-native/releases
| Version | RC release | Stable release |
| ------- | ------------------- | -------------- |
| 0.36.0 | week of October 10 | October 24 |
| 0.37.0 | week of October 24 | November 7 |
| 0.38.0 | week of November 7 | November 21 |
| 0.39.0 | week of November 21 | December 5 |
| 0.40.0 | week of December 5 | December 19 |
| 0.39.0 | week of November 21 | December 2 |
| 0.40.0 | 1st of December | 1st of January |
| 0.41.0 | 1st of January | 1st of February|
| ... | ... | ... |
-------------------
@ -84,11 +83,11 @@ When finished and there are breaking changes, include them in the release notes
Tweet about it! Link to release notes and say "please report issues" and link to the master issue to track bugs you created.
## IMPORTANT: Track bug reports from the community during the following two weeks, ping owners to get them fixed
## IMPORTANT: Track bug reports from the community during the following month, ping owners to get them fixed
A good way to do this is to create a github issue and post about it so people can report bugs. Examples: [#6087](https://github.com/facebook/react-native/issues/6087), [#5201](https://github.com/facebook/react-native/issues/5201)
**Only cherry-pick small and non-risky bug fixes**. **Don't pick new features into the release** as this greatly increases the risk of something breaking. The main point of the RC is to let people to use it for two weeks and fix the most serious bugs.
**Only cherry-pick small and non-risky bug fixes**. **Don't pick new features into the release** as this greatly increases the risk of something breaking. The main point of the RC is to let people to use it for a month and fix the most serious bugs.
-------------------
@ -121,7 +120,7 @@ node ./scripts/bump-oss-version.js <exact_version_you_are_releasing>
## How to do the final release (e.g. 0.22.0, 0.22.1)
Roughly two weeks after the branch cut (see the release schedule above) it's time to promote the last RC to a real release.
Roughly a month after the branch cut (see the release schedule above) it's time to promote the last RC to a real release.
Once all bugfixes have been cherry-picked and you're sure the release is solid (example: [#6087](https://github.com/facebook/react-native/issues/6087)), do the release: