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

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

• Development Spec Design draft complete
• Milestone checklist attached to Development spec

See: FIO Marketplace

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)
• Development Spec 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

N/A

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
• Do final merge to develop

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

Need to confirm the right code makes it in when we do the merge to develop.

In QA > Ready for UAT

Dev Server Testing

• Install release on DEV server

https://fioprotocol.atlassian.net/wiki/spaces/FC/pages/349601827/Frontend+Website+Documentation

http://198.199.122.78:4200

Merge to develop and install on DEV

• Rebase feature branch (Thomas)
• Merge to develop for UAT testing (Eric)

Feature complete

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

In UAT > Ready to Deploy

• UAT Complete (Product Management and other team members)
• 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

Devnet > Testnet

Merge to develop and install on DEV

• Rebase feature branch (Thomas)
• Merge to develop for UAT testing (Eric)

Early December

Devnet testing

• addaction and createfee for new actions in fio.devtools
• Release to Devnet using MSIGs
• Perform functional tests on Devnet, review results with team (add results to Dev Spec)
• Perform scalability and performance tests on Devnet (add results to Dev Spec)
• JS tests completed and run cleanly on Devnet
• Devnet fork test
• Perform the Testnet rollout verification for the feature and report findings (add results to Dev Spec)

Early December

History node testing

• Test against node with V1 History and confirm no errors in log file (add results to Dev Spec)

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

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)