Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 14 Next »

The milestone checklist tracks the release management tasks.

Task

Deliverables

Notes

Devnet

Testing

  • Devnet fork test (Dev lead)
  • Devnet performance test (Dev lead)

See: Bahamas (and migration) Devnet Test Plan

fio.contract

  • Run upgrade using set code and set abi (Dev lead)

N/A

New contract tests

  • Test ability to create new system contracts

Testnet

Communication

  • Socialize changes with all BPs on Testnet and the community and marketing (Eric)
  • Monitor and coordinate the rollout with BPs (Eric)

fio.test

  • Make sure there is a release/n.n.x_m.m.x branch for current production release (need to update with new commits)
  • Create release/n.n.x_m.m.x branch from develop, confirm it runs against new release

Pre-release build testing

  • Replay from Genesis
  • TBD: need list of other tests from Todd (or from BPs)

fio (chain)

  • Create pre-release (Testnet Release Candidate - FIO vx.x.x-rcx)
  • Generate .deb and .tgz build files using fio.package
  • Upload .deb and .tgz build files to AWS > S3 > fioprotocol > Mainnet for use with fio-docker
  • Update release notes
  • Track chain upgrade of BPs

Testnet validation

  • Run fio.test Testnet smoketest, confirm FIO Request getters still work
  • Confirm hashes of testnet (N/A - chain release only)
  • Get list of Testnet validation and tests from BPs
  • Confirm versions of testnet nodes

Mainnet

Mainnet prep

  • Create upgrade checklist of BPs and integration partners
  • Eric to work with Brit to coordinate Mainnet rollout plan with the BP, wallet, and exchange community, watch over the execution and help to ensure rollout is completed in full.
    • During rollout ask about get_sent_fio_requests, get_pending_fio_requests, and get_obt_data. Do they hit those endpoints directly, or do they do table lookups?
  • Socialize release changes with all BPs and the community and marketing
  • Perform Testnet rollout verification and report findings

fio.test

  • Merge release/2.3.x_3.0.x branch to master, create vn.n.n_m.m.m tag
  • Run test tag against new release

fio chain

  • Move pre-release to release (Release - FIO vx.x.x)
  • Generate .deb and .tgz build files using fio.package
  • Upload .deb and .tgz build files to AWS > S3 > fioprotocol > Mainnet for use with fio-docker
  • BP mainnet node upgrade checklist is complete (BP spreadsheet, or create one in Jira)
  • Perform the rollout verification and report findings
  • Scan API nodes to confirm server_version_string (will not catch everything, but a good check)

Done for 3.0.0

General

  • Move FIP status to Final and include release links
  • Update Initiative and Epic status

  • No labels