From aad40de3feb01f10c413f90f7c9d45a0de2a52c3 Mon Sep 17 00:00:00 2001 From: Ramiro Saenz Date: Tue, 4 Jul 2017 21:41:44 -0300 Subject: [PATCH] Updated DEPLOYMENT (markdown) --- DEPLOYMENT.md | 31 +++---------------------------- 1 file changed, 3 insertions(+), 28 deletions(-) diff --git a/DEPLOYMENT.md b/DEPLOYMENT.md index 4e8123f..9d96bc2 100644 --- a/DEPLOYMENT.md +++ b/DEPLOYMENT.md @@ -12,9 +12,9 @@ For branch steps: > `npm run sencha:compile:build` 6. Go to the **rambox-build** repo and commit and push changes. -2. Pull Request to _master_ using Github Desktop Client and check in GitHub page if the pull request was pushed. +2. Pull Request to _master_ using Github Desktop Client and change the name of the PR to "X.X.X". Then check in GitHub page if the pull request was pushed. 4. In this moment, you can see in the new PR that Travis is deploying the new version and pushed as Draft. -5. Once Travis finished successfuly, merge the PR to master changing the title and description to "X.X.X". Then change the title of the PR to "vX.X.X". +5. Once Travis finished successfully, merge the PR to master changing the title and description to "X.X.X". (TODO: at this time maybe Travis will start building again but it will fail, please prevent) 6. Change the release to pre-release to start AppVeyor. 6. In the meantime, edit the Release and define the **Changelog** and save it (still **Pre-Release**). 7. Change the [index.html](https://github.com/saenzramiro/rambox/blob/gh-pages/index.html) of the Website and [README.md](https://github.com/saenzramiro/rambox/blob/master/README.md) to update if is necessary. @@ -24,29 +24,4 @@ For branch steps: 11. Publish release in Github. 11. Go to **Heroku** instance and in Resources tab, disable Dynos and enable it again (if no version detected yet, we have to force it). 12. Go to [Rambox API](https://github.com/saenzramiro/rambox/tree/gh-pages/api) and update with the new version to notify users. -13. Publish message in social networks mentioning new services and send emails. - - -Follow this steps to deploy a new version of Rambox: - -1. Define Rambox version editing **app/package.json** and **appveyor.yml**. -1. Be sure to have the same dependencies from **package.json** and **app/package.json**. -1. Define Electron version in **package.json** and Travis CI Environment Variables. -1. Define **electron-builder** version in **package.json**. -2. Once commited all with Github Desktop Client, clean and build the project: - - > `npm run sencha:clean` - - > `npm run sencha:compile:build` -3. Go to the **rambox-build** repo and commit and push changes. -4. Create a new **Github Release** with the version and publish it as a **Pre-Release**. -5. AppVeyor and Travis will start building automatically. -6. In the meantime, edit the Release and define the **Changelog** and save it (still **Pre-Release**). -7. Change the [index.html](https://github.com/saenzramiro/rambox/blob/gh-pages/index.html) of the Website and [README.md](https://github.com/saenzramiro/rambox/blob/master/README.md) to update if is necessary. -8. Update Wiki if necessary. -9. Add new version in [Wiki CHANGELOG](https://github.com/saenzramiro/rambox/wiki/CHANGELOG). -10. Edit artifacts names for Linux and Windows x64, adding "-x64". Ex: "Rambox-0.4.2-x64.deb". -11. Publish release in Github. -11. Go to **Heroku** instance and in Resources tab, disable Dynos and enable it again (if no version detected yet, we have to force it). -12. Go to [Rambox API](https://github.com/saenzramiro/rambox/tree/gh-pages/api) and update with the new version to notify users. -13. Publish message in social networks mentioning new services and send emails. \ No newline at end of file +13. Publish a message to social networks mentioning new services and send emails. \ No newline at end of file