From 2c6d9d8e142b34c37ccec797d43a24af43a5799d Mon Sep 17 00:00:00 2001 From: Martin Konicek Date: Mon, 18 Jan 2016 20:40:13 +0000 Subject: [PATCH] Update Releases.md --- Releases.md | 31 +------------------------------ 1 file changed, 1 insertion(+), 30 deletions(-) diff --git a/Releases.md b/Releases.md index 5e37bfd4f909f5..70b184ff0bcb91 100644 --- a/Releases.md +++ b/Releases.md @@ -43,36 +43,7 @@ Make absolutely sure basic iOS and Android workflow works on master, see the ins ## Do a release -Publish to Maven Central (Note: **We could get rid of this whole section by publishing binaries to npm instead**): - - Log into Sonatype and go to [Staging upload](https://oss.sonatype.org/#staging-upload). You'll need to get permissions for this by filing a ticket explaining you're a core contributor to React Native. [Example ticket](https://issues.sonatype.org/browse/OSSRH-11885). - - Select Artifact(s) with a POM (to publish to a local Maven repo for testing run `./gradlew :ReactAndroid:installArchives`) - - Add all files: .aar, sources jar, javadoc jar, .asc for everything (including the POM file) - - Wait a few hours until you see the version has propagated to [JCenter](https://bintray.com/bintray/jcenter/com.facebook.react%3Areact-native/view) - -To release to npm: - -(You need to be a maintainer of the repo. For admins, here's the command to promote someone) - -``` -npm owner add react-native -``` - -``` -git tag v0.version_you_are_releasing.0-rc 0.version_you_are_releasing-stable # don't forget the `v` at the beginning! -git push --tags -``` - -- Publish to npm - -``` -npm set registry https://registry.npmjs.org/ -npm publish -# *Only* when doing a non-rc release: -# npm dist-tag add react-native@0.non_rc_version.0 latest -``` -- Upgrade tags to a release by going to https://github.com/facebook/react-native/tags -- Click "Add Notes to release" -- Click Publish +Skip this for now, ping @mkonicek on messenger and he'll handle it. Docs [here](https://github.com/facebook/react-native/blob/master/Releases-publish.md). ## Track bug reports from the community during the following two weeks and make sure they get fixed