Skip to content
This repository was archived by the owner on Nov 6, 2020. It is now read-only.
This repository was archived by the owner on Nov 6, 2020. It is now read-only.

Release next-beta 1.11 #8190

@5chdn

Description

@5chdn

Prepare Code:

  • Decide on a rough timeline, feature freeze, release date
    • Feature freeze: Apr 20, 2018
    • Estimated release: Apr 30, 2018
  • Do a reality-check against the roadmap-known-issues
  • Make sure UI related changes are done
    • Remove UI and Public Node completely
    • Replace :8180 with static page (link to docs, simple stats)
    • Remove (rework?) installers (code, ci, ...) and promote separate UI
  • Notify devs about a new beta release, ask to submit PRs
  • Create backports for all PRs tagged with B0-patch
  • Merge all pending pull requests that should be included in the next beta

Freeze Code:

  • archive stable branch to something like old-stable-1.9
    • change THIS_TRACK in code to oldstable
    • protect that branch in Github settings
  • merge beta branch to stable
    • and bump track (THIS_TRACK stable)
    • check ci scripts for stable or *1.9* specifics -> *1.10*
    • check the js/ui scripts from track specific stuff
  • merge master branch to beta
    • and bump track (THIS_TRACK beta)
    • check ci scripts for beta or *1.10* specifics -> *1.11*
    • check the js/ui scripts from track specific stuff
  • On master: bump minor and patch version in code to 1.12.0
    • Cargo.toml (version key)
    • util/version/Cargo.toml (version key)
    • nsis/installer.nsi (VERSIONMINOR and VERSIONBUILD keys)
    • mac/Parity.pkgproj (VERSION key)
    • mac/Parity/Info.plist (CFBundleShortVersionString)
    • cargo update -p parity-version
  • Run cargo update -p parity-version on the new branches
  • On stable: bump and consider a stable release

Conduct QA:

  • Check if Gitlab pipeline on beta and latest HEAD is green
  • Create a test tag for testing the full release pipeline, e.g., v1.11.0-rc0
  • Fix all issues with the test tag until CI is all green
  • Create a release tag, e.g., v1.11.0 on HEAD of beta, wait for binaries
  • Publish binaries for the tag only
  • Notify devs about available binaries for testing: https://vanity-service.parity.io/parity-binaries?format=markdown&version=v1.11.0
    • check all JSON consensus tests pass with all valid configurations
    • test invocation with each major CLI option
    • do a full sync on foundation network
    • check sync on ropsten and kovan
    • check if UI is doing what it is supposed to do

Publish Release:

  • Publish binaries and link beta-release for vanity service and docker (and/or stable-release)
  • update shut down the public nodes (wallet.parity.io, kovan-wallet.parity.io)
  • draft a new release in github, add sha256sums
  • update homebrew versions and checksums
  • release snapcraft beta (or stable), see CI for snap build ID
  • update one-line installer (should work automatically by now)
  • flush Cloudflare caches
  • verify that vanity-service returns proper versions (for stable and beta channels)
  • check & update download links at www.parity.io
  • authorize auto-update on operations proxy contract
  • update parity-news (and write a blog article)
  • update README, docker README, brew README
  • update Wiki and JSON-RPC API docs
  • push out to social networks
  • close the meta issue & the 1.11 milestone

Metadata

Metadata

Assignees

Labels

F9-meta 🔮A specific issue for grouping tasks or bugs of a specific category.F9-release 🎈A specific release. All such issues should be templated on #1387.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions