[FIP-6,21] Development Milestone Checklist
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 | Design should include all elements outline in the Development Spec template including:
| |
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 | TODO: Todd to test in testnet phase | |
Unit testing |
| |
In QA > Ready for UAT |
|
|
Merge to release branch and install on DEV |
| |
Feature complete | Develop branch on DEV server | |
In UAT > Ready to Deploy |
|
|
| ED to review test results with Pawel | |
Ready to Deploy > Devnet |
|
|
Rollout planning |
| |
Devnet > Testnet |
|
|
Devnet testing |
| |
History node testing | For transfer locked tokens, we need to confirm that the new account creation action shows up in History. | |
Testnet > Mainnet |
|
|
Testnet rollout verification |
| |
Post-release |
|
|
Mainnet rollout verification |
|