Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

The milestone checklist tracks the development tasks that need to be completed prior to moving the Epic or story into a new status

Tasks

Deliverables / Notifications

Github repo

  • Excluded
  • Included
  • Create bug/feature branch

See: https://developers.fioprotocol.io/docs/developers/git

https://github.com/tvl83/fio.contracts/tree/bugfix/fioescrow

Dev Epic

  • Excluded
  • Included
  • Create epic to track development work (may be done by project manager)

BD-3666 - Getting issue details... STATUS

Requirements, Design, and Scoping

Meeting - Kickoff meeting

  • Excluded
  • Included
  • Kickoff meeting held with Product Manager to review requirements

Met with team on 4/25/22 to review hotfix.

Complete FIP (if applicable)

  • Excluded
  • Included
  • FIP reviewed and moved to Accepted status

Complete functional / technical design

  • Excluded
  • Included

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.

BD-3667 - Getting issue details... STATUS

Scoping

  • Excluded
  • Included
  • 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

  • Excluded
  • Included
  • Functional spec approved by architecture champions and team

Finalize FIP

  • Excluded
  • Included
  • FIP updated with any changes resulting from design review

Development

Project management

  • Excluded
  • Included
  • Maintain status in Epic Summary

  • Project milestones

  • Time estimates for reaching project milestones

BD-3666 - Getting issue details... STATUS

RAM bumps for new actions

  • Excluded
  • Included
  • 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

  • Excluded
  • Included
  • 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)

  • Excluded
  • Included
  • FIP / development spec updated to reflect the details of the implementation

ABI validation

  • Excluded
  • Included
  • 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

  • Excluded
  • Included
  • Code reviewed with dev team

BD-3668 - Getting issue details... STATUS

Unit Testing

Action and getter testing

  • Excluded
  • Included
  • fio.test test branch created
  • fio.test enhanced with initial action and getter tests
  • Tests run cleanly

BD-3669 - Getting issue details... STATUS

Performance testing

  • Excluded
  • Included
  • 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

  • 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

System Testing

System testing

  • Excluded
  • Included
  • Tests passed to QA for system testing

BD-3670 - Getting issue details... STATUS

UAT

Merge to release or develop and install on DEV

  • Excluded
  • Included
  • 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.

BD-3671 - Getting issue details... STATUS

Feature complete

  • Excluded
  • Included
  • All bugs and outstanding items completed
  • Work with QA to confirm JS tests run cleanly against DEV server

BD-3672 - Getting issue details... STATUS

Product signoff

  • Excluded
  • Included
  • Signoff from Product Management

This is feature or bug specific signoff from Product Management so is controlled by the lead developer.

BD-3673 - Getting issue details... STATUS

Devnet

Devnet testing

  • Excluded
  • Included
  • Work with release engineer to fully test any new contracts and actions.

Devnet testing is tracked in the Release Milestone Checklist

Testnet

Test planning

  • Excluded
  • Included
  • Work with release team to ensure correct Testnet rollout (addaction, setfee, contract updates, etc).

See Release Milestone Checklist

Testnet rollout verification

  • Excluded
  • Included
  • Perform the Testnet rollout verification for the feature and report findings (add results to Dev Spec)

BD-3674 - Getting issue details... STATUS

Mainnet

Test planning

  • Excluded
  • Included
  • Work with release team to ensure correct Mainnet rollout (addaction, setfee, contract updates, etc).

See Release Milestone Checklist

Mainnet rollout verification

  • Excluded
  • Included
  • Perform the Mainnet rollout verification for the feature and report findings (add results to Dev Spec)

BD-3675 - Getting issue details... STATUS

  • No labels