Release next-beta 1.8.0.

[5chdn]

Step 1: Wind up development:

• check for known bugs (feel free to add tickets here, bold are blockers)
  • #4833 metropolis release core consensus
  • #5968 panicked; qed; core
  • #6280 sync io / disk usage core
  • #6326 shutdown corrupts db core
  • #6372 warp sync not warpy core
  • #6418 util refactor 0 core
  • #6484 warp sync fail core
  • #6485 graceful exit wrong cli falgs core
  • #6534 badge display ui picops
  • #6549 token balances ui polkadot
  • #6593 main net sync stuck core
  • #6637 missing responses eth_get_logs core
  • #6657 warp sync on archive node? core
  • #6658 tokens again ui polkadot
  • #6667 signer not working public node picops polkadot
  • #6669 misleading error ui
  • #6693 util refactor 1 core
  • #6700 dapp reg broken dapp ui polkadot
• notify devs to submit any remaining PRs
• merge any outstanding PRs
  • #6664 fix build warnings core
  • #6686 potential modexp len overflow core consensus
  • #6687 difficulty tests core
  • #6690 separate migrations util core
  • #6691 warp sync archive node core
  • #6694 prevent going offline while warp sync core
  • #6701 fix address selector ui
  • #6702 fix ascii to hex rpcapi
  • #6705 remove deps rustc_serialize core
  • #6707 signer signs data ui
  • #6708 public node signer fix ui
  • #6710 vouchfor display ui
  • #6711 graceful exit cli flags core
  • #6714 fix gas estimation dapps ui
  • #6718 returndata out of bounds check core consensus
  • #6719 check vouch status ui
  • #6723 reject invalid cli flags core
  • #6725 fix tokens and badges ui
  • #6730 badges again ui
  • #6741 modexp again core consensus

Step 2: Conduct QA:

• ask all core devs for QA sign off
• check all JSON consensus tests pass with all valid configurations
• do a full sync
• deploy netstats node
• test invocation with each major CLI option

Step 3: Conduct release:

• merge beta branch to stable and bump patch version (THIS_TRACK stable)
• merge master branch to beta and bump patch version (THIS_TRACK stable)
• new tag for specific version (i.e. 1.7.0-stable) on HEAD of stable.
• new tag for specific version (i.e. 1.8.0-beta) on HEAD of beta.
• update all versions in master (Cargo.toml, windows installer, macos installer)
  • Cargo.toml (version key)
  • util/Cargo.toml (version key)
  • nsis/installer.nsi (VERSIONMINOR and VERSIONBUILD keys)
  • mac/Parity.pkgproj (VERSION key)
  • cargo update -p ethcore-util
• prepare any binaries that are manual for both beta and stable
  • homebrew versions and checksums

Step 4: Publish release:

• new release in github, add sha256sums
• authorize auto-update on operations proxy contract
• update parity-news (maybe add blog article)
• set up all binary paths on wiki
• set up all binary paths on install guides
• bump website so it's tracking master (i.e. 1.9) progress
• update README and wiki
• push out to social networks
• close this issue & the 1.8 milestone

[roninkaizen]

great overview-
thank you!

[5chdn]

@roninkaizen It's not everything that is in 1.8, just the last-minute open tasks.

[5chdn]

takeaways:

• more clear communication of feature-freeze.
• check if UI is doing what it is supposed to do.
• kovan sync was broken. check all networks.
• auto-updater required patch. check auto-updater.
• one-line installer and homebrew should always point to beta.
• update readme, docker readme, brew readme.
• update api docs (json-rpc).
• in general more QA before release.

björn:

• maybe add "update wallet.parity.io & kovan-wallet.parity.io" to release task list?