Skip to content

Release plan template

Wes Morgan edited this page Nov 2, 2019 · 5 revisions

Copy this for new release plans to ensure the things we want to do every time get done. (And delete this from the copy.)

  • Blockers
    1. (insert new blockers here)
    2. Roll a new Go SDK release (same version) and update tupelo to use it.
    3. Roll a new WASM SDK release with the latest Go SDK & other bits compiled in.
    4. Make sure every component is using a release tag of every dependency possible (i.e. not a commit); especially our internal libraries.
    5. Benchmarks and testing are sufficiently stable & performant.
    6. All integration tests pass.
    7. Run the AWS performance profiler and consider posting results.
    8. Product signs off.
    9. Confirm whether state files in home directory need to be deleted for release and document on docsite.
  • Nice to haves
  • Must not includes
  • Process & infrastructure improvements
  • Post-release
    1. Update TestNet to released version
Clone this wiki locally