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

Release next-beta 1.9.0 #7071

Closed
58 of 64 tasks
5chdn opened this issue Nov 16, 2017 · 5 comments
Closed
58 of 64 tasks

Release next-beta 1.9.0 #7071

5chdn opened this issue Nov 16, 2017 · 5 comments
Assignees
Labels
F9-release 🎈 A specific release. All such issues should be templated on #1387. P0-dropeverything 🌋 Everyone should address the issue now. Q7-involved 💪 Can be fixed by a team of developers and probably takes some time.
Milestone

Comments

@5chdn
Copy link
Contributor

5chdn commented Nov 16, 2017

Step 0: Tighten Roadmap:

  • Decide on rough timeline
    • Feature freeze: Dec 31, 2017
    • Estimaged release: Jan 22, 2018
  • Decide on important features to be inlcuded
    • User Interface 2.0
    • Bug Fixes, bug fixes, bug fixes, ...

Step 1: Wind up development:

Step 2: Conduct QA:

  • hire someone for QA
    • 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.

Step 3: Conduct release:

  • archive stable branch to something like old-stable-1.7(THIS_TRACK oldstable)
  • merge beta branch to stable and bump patch version (THIS_TRACK stable)
  • merge master branch to beta and bump patch version (THIS_TRACK beta)
  • new tag for specific version (1.8.7 and stable-release) on HEAD of stable.
  • new tag for specific version (1.9.0 and beta-release) on HEAD of beta`.
  • update all versions in master to 1.10.0 (Cargo.toml, windows installer, macos installer)
    • 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
  • prepare any binaries that are manual for both beta and stable
  • update public nodes (wallet.parity.io, kovan-wallet.parity.io)

Step 4: Publish release:

  • new release in github, add sha256sums
  • update homebrew versions and checksums
  • update one-line installer
  • flush Cloudflare caches
  • verify that vanity-service returns proper versions (for stable and beta channels)
  • 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 this issue & the 1.9 mileston
@5chdn 5chdn added F9-release 🎈 A specific release. All such issues should be templated on #1387. P5-sometimesoon 🌲 Issue is worth doing soon. Q7-involved 💪 Can be fixed by a team of developers and probably takes some time. labels Nov 16, 2017
@5chdn 5chdn added this to the 1.9 milestone Nov 16, 2017
@5chdn 5chdn self-assigned this Nov 16, 2017
@debris
Copy link
Collaborator

debris commented Nov 18, 2017

and let's schedule the next release for Jan 8th (7 weeks, because of Christmas)

@5chdn
Copy link
Contributor Author

5chdn commented Nov 20, 2017

And feature freeze Dec 22nd?

@debris
Copy link
Collaborator

debris commented Nov 21, 2017

y

@5chdn
Copy link
Contributor Author

5chdn commented Dec 8, 2017

We need to finalize the rebranding in 1.9

@5chdn 5chdn added P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. and removed P5-sometimesoon 🌲 Issue is worth doing soon. labels Dec 15, 2017
@5chdn
Copy link
Contributor Author

5chdn commented Jan 2, 2018

Remove expanse #7146

@5chdn 5chdn added P0-dropeverything 🌋 Everyone should address the issue now. and removed P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. labels Jan 3, 2018
@5chdn 5chdn closed this as completed Jan 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F9-release 🎈 A specific release. All such issues should be templated on #1387. P0-dropeverything 🌋 Everyone should address the issue now. Q7-involved 💪 Can be fixed by a team of developers and probably takes some time.
Projects
None yet
Development

No branches or pull requests

2 participants