[FIP-26] Development Milestone Checklist (FIO Marketplace)
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 | |
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 | |
Finalize FIP | FIP updated with any changes resulting from design review | |
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 | |
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) | |
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 |
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) | |
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) | ย |