Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The milestone checklist tracks the development tasks that need to be completed prior to moving the Epic or story into a new status

...

Task

...

Deliverables

...

Notes

...

In Definition > Ready for Review

...

Complete FIP (if applicable)

...

  •  FIP reviewed and moved to Accepted status

...

https://github.com/fioprotocol/fips/blob/master/fip-0026.md

...

Complete functional / technical design

...

...

Ready for Review > Ready for Dev

...

Design review

...

  •  Functional spec approved by architecture champions and team

...

Frontend Website Documentation

...

Finalize FIP

...

  •  FIP updated with any changes resulting from design review

...

https://github.com/fioprotocol/fips/blob/master/fip-0026.md

...

In Development > Ready for QA

...

Code complete

...

  •  Development branch created and initial merge completed
    •  fio
    •  fio.contract
  •  Code reviewed with dev team (thorough review of modified methods and files)
  •  FIP updated to reflect the details of the implementation
  •  Validate json for any new ABIs or ABIs that have been updated

...

https://fioprotocol.atlassian.net/browse/BD-2449

...

SDKs

...

  •  Stories created for any needed SDK updates (new getters or actions)
  •  SDK dev complete
  •  All SDK unit tests run cleanly
    •  fiosdk_typescript
    •  fiosdk_kotlin

...

Needed?

...

Performance testing

...

  •  First level performance testing results reviewed with architecture champions (can be performed on dev machine, try to uncover any obvious perf limits)

...

https://fioprotocol.atlassian.net/browse/BD-2883

...

Unit testing

...

  •  fio.test enhanced with functional tests
  •  Tests run cleanly
  •  Functional tests well documented (in fio.test) and reviewed with team

...

https://fioprotocol.atlassian.net/browse/BD-2596

...

In QA > Ready for UAT

...

Merge to develop and install on DEV

...

  •  Rebase feature branch and merge to develop for UAT testing
  •  Install release on DEV server

...

Feature complete

...

  •  All bugs and outstanding items completed
  •  JS tests completed and run cleanly against DEV server

...

Develop branch on DEV server

...

In UAT > Ready to Deploy

...

  •  Signoff from Product Management

...

Ready to Deploy > Devnet

...

Rollout planning

...

  •  Create rollout/release plan for this effort (added actions, removed actions, table migrations, order dependent detailed instructions on how to roll out these changes successfully. include all necessary MSIGs)
  •  Detailed instructions on how to verify that the rollout was performed successfully
  •  Review the rollout plan and verification with architecture champions

...

Testnet > Mainnet

...

Testnet rollout verification

...

  •  Perform the Testnet rollout verification for the feature and report findings (add results to Dev Spec)

...

Post-release

...

Mainnet rollout verification

...

  •  Perform the Mainnet rollout verification for the feature and report findings (add results to Dev Spec)

...

  •  

See: [FIP-26] Development Milestone Checklist (FIO Marketplace)