-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* fix etherscan links * fix * code review fixes * add release commands * don't wait for build-to-process * bump version * ios build succesful * bump android version * android build * added release info * Fix new lines * Update RELEASE.MD * Update RELEASE.MD
- Loading branch information
Bruno Barbieri
authored
Dec 18, 2018
1 parent
36473f0
commit 025343b
Showing
8 changed files
with
63 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
## iOS release | ||
|
||
1 - Make sure you have fastlane installed (`sudo gem install fastlane`) | ||
|
||
2 - Bump the version number in `info.plist` and commit the change | ||
|
||
3 - Run `npm run release:ios` | ||
|
||
4 - Wait for the appstore email that the build has completed processing (10 min - 1 hour) | ||
|
||
5 - Go to this url: https://appstoreconnect.apple.com/WebObjects/iTunesConnect.woa/ra/ng/app/1438144202/testflight?section=iosbuilds | ||
|
||
6 - Click on the version number and then click on the "Test Details" tab | ||
|
||
7 - Enter the release notes and save | ||
|
||
8 - Click on the "Testers" tabs | ||
|
||
9 - Click on the `+` sign next to Groups and select Alpha. | ||
|
||
|
||
|
||
## Android release | ||
|
||
1 - open android/app//build.gradle and change the version number | ||
|
||
2 - Save and commit | ||
|
||
3 - Run `npm run release:android` | ||
|
||
4 - Go to the playstore: https://play.google.com/apps/publish/?account=9089866037123936197 | ||
|
||
5 - Click on the App logo, then go to Release Management >> App releases | ||
|
||
6 - Go to "Manage" inside "Closed track" (ALPHA) | ||
|
||
7 - Click Create Release | ||
|
||
8 - Drag the APK | ||
|
||
9 - Add Release notes at the bottom | ||
|
||
10 - Click review | ||
|
||
11 - Start rollout to ALPHA | ||
|
||
|
||
### Once you're done with both stores: | ||
- Submit a PR with the changes | ||
- Once it's merged create a tag on master for that version | ||
- Go to the release pages and create a new release for that tag, including the changelog | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters