Release 0.7.0

[micahalcorn]

NOTE: This checklist is generated from RELEASE.md when beginning the release procedure.

Prepare a release candidate

Release branches should be created well before a release is ready to be published. Sometime after a prior release has been merged and once all of a release's planned features have been merged to develop, a new branch should be created from develop:

• [x] origin-dapp: Create a release branch (if applicable)
  • git checkout -b release-0.3.0 develop
• [x] origin-js: Create a release branch (if applicable)
  • git checkout -b rerelease-0.7.0 develop (Note the re, due to July 1 git mixup)
• [x] origin-bridge: Create a release branch (if applicable)
  • git checkout -b release-0.2.0 develop

No additional features should be added to this release branch. Only bug fixes should be merged directly to the release branch, which itself should eventually be merged back to develop in the Publish step.

---

Set up -test branch of repos?

Confirm readiness

• [x] origin-js : In package.json, confirm version is 0.7.0
• [x] origin-js: Confirm js tests passing
  • docker-compose -f docker-compose-test.yml up origin-js-test
• [ ] Confirm release branches run locally in production mode.
  • This will build the DApp, using the locally symlinked origin-js. This can be done outside of origin-box, but you'll need to have a local blockchain running for it to connect to.
  • Do the build (Takes several minutes)
    npm run build
  • Serve from local webserver
    cd build && python -m SimpleHTTPServer 8000
  • Open the dapp in browser
    open 0.0.0.0:8000

Smart contract migrations

• [x] Confirm deployment accounts have eth for gas.
  • Both accounts [0] and [1] need gas, as test listings are created from [1].
  • Set mnemonic
  • export RINKEBY_MNEMONIC="_____"
  • export ROPSTEN_MNEMONIC=$RINKEBY_MNEMONIC
  • npm run scripts/deploy_checklist.js
  • [x] Rinkeby (Faucet)
  • [ ] Social proof URL: https://twitter.com/KeystonePaperCo/status/1012803664509952001
  • [ ] account[0] 0xfF2BA846ab52EDBd724A5ef674AbF5A763849B61
  • [ ] account[1] 0x3003F9dCFDC17e63cfe7023130B804829b369882
  • [x] Ropsten (Faucet)
  • [ ] account[0] 0xfF2BA846ab52EDBd724A5ef674AbF5A763849B61
  • [ ] account[1] 0x3003F9dCFDC17e63cfe7023130B804829b369882

Test on Heroku

• [x] Confirm release branches run locally in production mode.
  • npm run build
    # This will generate build directory
  • cd build && python -m SimpleHTTPServer 8000
    # Serve from local webserver
  • open 0.0.0.0:8000
    # Open the dapp in browser

---

Publish

origin-js

• [x] If contracts have changed:
  • Show diff with: git diff master..develop contracts/contracts/
  • cd contracts
  • [x] Deploy new smart contracts to Ropsten. Be sure addresses are listed in ABI files.
  • npx truffle migrate --reset --network ropsten | tee releases/0.7.0_ropsten.log
  • [x] Deploy new smart contracts to Rinkeby. Be sure addresses are listed in ABI files.
  • npx truffle migrate --reset --network rinkeby | tee releases/0.7.0_rinkeby.log
  • [x] Migrate data from old contracts to new. (Once we get around to writing migrations!)
  • [ ] origin-js: Build origin.js (in dist/origin.js) -- Not redundant: This will bake in the new contract addresses into the contract's .json files.
  • npm run install:dev
• [ ] origin-js: Merge and push branches
  • git checkout develop
  • git merge --no-ff rerelease-0.7.0
  • git push
  • git checkout master
  • git merge --no-ff rerelease-0.7.0
  • git push
• [ ] origin-js: Delete release branch
  • git branch -D rerelease-0.7.0
  • Manually delete on GitHub
• [ ] origin-js: Create new GitHub release with origin.js code,
  • [ ] Version in form v0.7.0 (This will add git tag on master)<<<<<<< HEAD
  • [ ] Include output of Truffle logs (containing addresses of smart contracts) in description
  • [ ] Include block number the contracts were deployed at
  • https://rinkeby.etherscan.io/address/<contract address>
  • ex. https://rinkeby.etherscan.io/address/0x29d260c47411a0b9eeeb087925afa759914b0d2f
• [ ] origin-js: Publish to npm.
  • npm publish

origin-dapp

• [ ] origin-dapp: Build against npm version. This will update package-lock.json
  • npm unlink --no-save origin && npm install && npm run build
• [ ] git add package.json && git commit -m "0.3.0 release"
• [ ] origin-dapp: Merge and push branches
  • git checkout develop
  • git merge --no-ff release-0.3.0
  • git push
  • git checkout master
  • git merge --no-ff release-0.3.0
  • git push
• [ ] origin-js: Delete release branch
  • git branch -D release-0.3.0
  • Manually delete on GitHub
• [ ] origin-dapp: Confirm that origin-dapp works when run alone again NPM.
• [ ] origin-dapp: Test deploy dapp to heroku
  • git clone https://github.com/OriginProtocol/origin-dapp && cd origin-dapp
  • heroku create && git push heroku master
• [ ] origin-dapp: Add git tag to master to match origin-js.
  • git tag -a v0.3.0 -m "New release"

origin-bridge

• [ ] origin-dapp: Merge and push branches
  • git checkout develop
  • git merge --no-ff release-0.2.0
  • git push
  • git checkout master
  • git merge --no-ff release-0.2.0
  • git push
• [ ] origin-js: Delete release branch
  • git branch -D release-0.2.0
  • Manually delete on GitHub
• [ ] origin-bridge: Add git tag to master to match origin-js.
  • git tag -a v0.2.0 -m "New release"

Follow-up

• [ ] Confirm published origin.js file is accessible via code.originprotocol.com redirect
  • https://code.originprotocol.com/origin-js/origin-v0.7.0.js
• [ ] origin-dapp npm unlink --no-save origin
• [ ] origin-dapp: Confirm that "one-line setup & run" command works on master branch shown by default
• [ ] origin-js: Increment version number to on develop to for next release
  • git checkout develop
  • subl package.json
• [ ] git push
• [ ] docs: Review docs for needed updates. Confirm example code on playground site (jsfiddle?) still work.
• [ ] Copy this to-do list into new issue for next sprint.
• [ ] Post notice of new release on Discord

Troubleshooting

• Error: insufficient funds for gas * price + value
  • Not enough funds in primary or secondary account. Usually hits when I forget to put funds in second account and it trys to deploy sample listings.

[micahalcorn]

@wanderingstan I think this existing issue is appropriate for our next release of Origin.js around the end of the 📆 sprint.

[wanderingstan]

@micahalcorn I agree! 👍

[tyleryasaka]

@micahalcorn @wanderingstan We need to add another step for origin-bridge:

• [ ] Copy contract ABIs from origin-js (located in contracts/build/contracts) to origin-bridge (located in contracts)

☝️ must happen after new contracts have been deployed to test nets!

[wanderingstan]

@tyleryasaka fantastic -- Can you modify RELEASE.md directly (or PR)? (It was a great idea for you to make that file--a standard source of truth for our procedure!)

I think the protocol for beginning a release will be to copy over the latest from that that file into an issue like this.

[tyleryasaka]

Done. https://github.com/OriginProtocol/origin-js/commit/d9ee9bc86046287685a18117071aba9ceb12700f

Commit number 666. Should I be worried? 😱

[micahalcorn]

I'm going to consider this done. 🍾

[wanderingstan]

🥂