-
-
Notifications
You must be signed in to change notification settings - Fork 144
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
21 changed files
with
487 additions
and
327 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
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,105 @@ | ||
# Re-com Release Procedure | ||
|
||
## Setting your environment up | ||
|
||
A number of things need to be set up before the release procedure can commence. | ||
|
||
### GPG | ||
|
||
Here are the basic instructions to follow to get GPG running: https://github.com/technomancy/leiningen/blob/stable/doc/GPG.md | ||
|
||
A few notes for Windows: | ||
|
||
- The recommended gpg version for windows is: http://www.gpg4win.org. | ||
- There are several version on the download page. I used the "Vanilla" one. Direct link: http://files.gpg4win.org/gpg4win-vanilla-2.2.4.exe | ||
- To display your public key, just type: `gpg --export -a`. | ||
|
||
### Clojars | ||
|
||
Simply need to set up your own account, then get the Day8 Clojars admin to add you to the family. Then you can publish to Day8 Clojars. | ||
|
||
Note that your GPG public key from above needs to be pasted into your Clojars profile for this process to work. | ||
|
||
More info on deploying libraries using lein: https://github.com/technomancy/leiningen/blob/master/doc/DEPLOY.md | ||
|
||
## Release Steps | ||
|
||
### Build library and test the demo | ||
|
||
Note that all these commands are entered at the repo root folder. | ||
|
||
- [ ] Close all auto-compiles (command line and/or IntelliJ). | ||
- [ ] Build each of these aliases (will require separate terminals for each): | ||
- `lein debug` | ||
- `lein debug-prod` | ||
- `lein debug-test` | ||
- [ ] For `dev` and `prod`, run through each demo page and make sure no errors or debug output appears in the console. | ||
- [ ] For `test`, make sure all tests pass. Modify code/tests until all tests pass. | ||
- [ ] Close all auto-compiles again. | ||
|
||
### Make a Github release | ||
|
||
- [ ] TODO: IntelliJ should be able to do all of these steps as it has integrated gitflow - investigate. | ||
- [ ] Make sure your master branch is up-to-date with Github (in 99% of cases it will be): | ||
- `git checkout master` (TODO: might have to shelve develop or feature branch outstanding changes - confirm). | ||
- `git pull` | ||
- `git checkout {the branch you are working in}` | ||
- [ ] Start a new release: | ||
- `git checkout develop` (TODO: may just need to be in the branch you are working in - confirm). | ||
- `git flow release start x.x.x` | ||
- A branch called 'release/x.x.x' is created. | ||
- [ ] Bump version in project.clj to `x.x.x`. | ||
- [ ] Update README.md file if required. | ||
- [ ] Commit to develop or finish feature: | ||
- `git commit -a -m "..."` | ||
- [ ] Push develop to GitHub: | ||
- `git push` | ||
- [ ] Finish the release: | ||
- `git flow release finish 'x.x.x'` | ||
- Merges develop into master. | ||
- Creates a tag with that version number. | ||
- Pops up an editor to describe the release. I just put "Version x.x.x". | ||
- Deletes the release branch. | ||
- [ ] Push develop to GitHub: | ||
- `git push` | ||
- [ ] Go to master branch: | ||
- `git checkout master` | ||
- [ ] Push master to GitHub: | ||
- `git push` | ||
- [ ] Push the tags to GitHub: | ||
- `git push --tags` | ||
- [ ] Create a GitHub Release: | ||
- Go to: https://github.com/Day8/re-com/releases | ||
- Should see your version `x.x.x` tag at the top. | ||
- Press the `Draft a new release` button. | ||
- Select this new `x.x.x` version in the Tag version dropdown. | ||
- Make sure this is based on a Target of master. | ||
- For the title, enter the version number: `x.x.x`. | ||
- Enter a description that includes a list of "Changes" and "Fixes" (since the last release). | ||
- Click the `Publish release` button. | ||
|
||
### Push library to Clojars | ||
|
||
- [ ] Push this release to Clojars: | ||
- `lein deploy clojars` | ||
- Will prompt for your Clojars username and password. | ||
- Will also prompt for your GPG passphrase. | ||
- [ ] "Promote" the Clojars release: | ||
- Go to the re-com Clojars page for this version: https://clojars.org/re-com | ||
- Log in. | ||
- Click on the link for this new version. | ||
- Click the big blue button at the bottom of the release page to make it live. | ||
|
||
### Deploy demo to AWS | ||
|
||
- [ ] Deploy demo to AWS: | ||
- `lein s3-static-deploy` | ||
- Could have used `lein deploy-aws` but this also builds the `prod` version which we have already just built. | ||
- Manually change `index.html` to `index_prod.html` in S3 Browser. TODO: Find a way to automate this. | ||
- Test it: http://re-demo.s3-website-ap-southeast-2.amazonaws.com. | ||
|
||
### Final tasks | ||
|
||
- [ ] Reply to all issues and pull requests relating to this release. | ||
- [ ] Post a note in #re-com Slack channel pointing to GitHub release page. | ||
- [ ] Post to Google Groups if necessary. |
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
Oops, something went wrong.