| | Tasks | Deliverables / Notifications |
---|
Links | | | |
Github repo | | - Create bug/feature branch
See: https://developers.fioprotocol.io/docs/developers/git | https://github.com/tvl83/fio.contracts/tree/bugfix/fioescrow |
Dev Epic | | - Create epic to track development work (may be done by project manager)
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | BD-3666 |
---|
|
|
Requirements, Design, and Scoping | | | |
Meeting - Kickoff meeting | | - Kickoff meeting held with Product Manager to review requirements
| Met with team on 4/25/22 to review hotfix. |
Complete FIP (if applicable) | | - FIP reviewed and moved to Accepted status
| |
Complete functional / technical design | | Design Draft should include a first draft of all elements outlined in the Development Spec. | Since this is a hotfix, the design is included in the Jira story. Jira Legacy |
---|
server | System JIRA |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | BD-3667 |
---|
|
|
Scoping | | - Create project stories for development for each of the remaining tasks that are included with the release
- Estimate stories
Each story should be unit of work that is deliverable in a 2 week sprint. An initial estimate should be included with every development story. | Development is already complete for this fix. |
Design Review | | | |
Design review | | - Functional spec approved by architecture champions and team
| |
Finalize FIP | | - FIP updated with any changes resulting from design review
| |
Development | | | |
Project management | | - Maintain status in Epic Summary
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | BD-3666 |
---|
|
|
RAM bumps for new actions | | - Determine RAM allocation for new actions and set RAM bump accordingly. This informationshould be added to the FIP.
See: https://developers.fioprotocol.io/docs/developers/ram | |
Fees for new actions | | - Estimate initial fees for all actions. In cases where the action requires additional RAM, the fees should be correlated with the RAM estimates. This informationshould be added to the FIP.
| |
Update FIP (or development document) | | - FIP / development spec updated to reflect the details of the implementation
| |
ABI validation | | - Validate json for any new ABIs or ABIs that have been updated
- If deploying new contract, make sure ABI copy command is in fio.devtools contracts/build.sh
| |
Code review | | - Code reviewed with dev team
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | BD-3668 |
---|
|
|
Unit Testing | | | |
Action and getter testing | | - fio.test test branch created
- fio.test enhanced with initial action and getter tests
- Tests run cleanly
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | BD-3669 |
---|
|
|
Performance testing | | - First level performance testing results reviewed with architecture champions (can be performed on dev machine, try to uncover any obvious perf limits)
| |
Release Plan | Rollout planning | | | |
Msig deployment plan | | - 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 and QA/Integration teams
- (or add to) wiki page in Releases directory to track any msigs needed to deploy the feature
Example: [fio 3.3 fio.contracts 2.7] msig deployment | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | BD-3677 |
---|
|
|
System Testing | | | |
System testing | | - Tests passed to QA for system testing
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | BD-3670 |
---|
|
|
UAT | | | |
Merge to release or develop and install on DEV | | - Rebase feature branch and merge to develop or feature branch for UAT testing
- Install release on DEV server
This is a developer task to ensure that their feature or fix is on a publicly accessible DEV server so it can be reviewed by Product Management. This should be done after system testing is complete. | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | BD-3671 |
---|
|
|
Feature complete | | - All bugs and outstanding items completed
- Work with QA to confirm JS tests run cleanly against DEV server
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | BD-3672 |
---|
|
|
Product signoff | | - Signoff from Product Management
This is feature or bug specific signoff from Product Management so is controlled by the lead developer. | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | BD-3673 |
---|
|
|
Devnet | | | |
Devnet testing | | - Work with release engineer to fully test any new contracts and actions.
| Devnet testing is tracked in the Release Milestone Checklist |
Testnet | | | |
Test planning | | - Work with release team to ensure correct Testnet rollout (addaction, setfee, contract updates, etc).
| See Release Milestone Checklist |
Testnet rollout verification | | - Perform the Testnet rollout verification for the feature and report findings (add results to Dev Spec)
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | BD-3674 |
---|
|
|
Mainnet | | | |
Test planning | | - Work with release team to ensure correct Mainnet rollout (addaction, setfee, contract updates, etc).
| See Release Milestone Checklist |
Mainnet rollout verification | | - Perform the Mainnet rollout verification for the feature and report findings (add results to Dev Spec)
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d |
---|
key | BD-3675 |
---|
|
|