Task | Deliverables | Notes |
|---|
In Definition > Ready for Review | | |
Complete FIP (if applicable) | - FIP reviewed and moved to Accepted status
| |
Complete functional / technical design | | Design should include all elements outline in the Development Spec template including: Technical design Functional test plan Performance test plan
|
Ready for Review > Ready for Dev | | |
Design review | - Design approved by architecture champions and team
- Functional test cases created and reviewed with architecture champions
- Performance test plan created and reviewed with team
| |
Finalize FIP | - FIP updated with any changes resulting from design
| TODO: Ed to review FIP |
In Development > Ready for QA | | |
Code complete | - Code reviewed with dev team. (multi day process with several meetings getting into the nitty gritty of modified methods and files)
- Design documents updated to reflect the details of the implementation
- Functional test plan results reviewed with architecture champions (review findings and iterate to address any concerns)
| |
SDKs | - Stories created for any needed SDK updates (new getters or actions)
- SDK dev complete
- All SDK unit tests run cleanly
| TODO |
Performance testing | - First level performance testing results reviewed with architecture champions (can be performed on dev box, try to uncover any obvious perf limits)
| TODO: Todd to test in testnet phase |
Unit testing | - fio.test enhanced with functional and performance tests, tests run cleanly on dev branch
| fio: release/2.0.x-dev fio.contracts: project/charlie fio.test: project/charlie fiosdk_typescript: develop
|
In QA > Ready for UAT | | |
Merge to release branch and install on DEV | - Rebase feature branch and merge to release branch 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 (includes review of test results)
| ED to review test results with Pawel |
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 | | |
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)
| |
History node testing | - Test against node with V1 History and confirm no errors in log file (add results to Dev Spec)
| For transfer locked tokens, we need to confirm that the new account creation action shows up in History. |
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)
| |