[FIP-42] Development Milestone Checklist

Owned by Eric Butz
Last updated: Jan 05, 2023
3 min read

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

 

 

Tasks

Deliverables / Notifications

Links

 

 

 

Github repo

 

Create bug/feature branch

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

 

Dev Epic or Story

 

Project manager will create initial Epic or Story

https://fioprotocol.atlassian.net/browse/BD-3730

Requirements, Design, and Scoping

 

 

 

Meeting - Kickoff meeting

Excluded
Included
Kickoff meeting held with Product Manager to review requirements

 

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.

 

Scoping

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.

 

Design Review

 

 

 

Design review

 

Finalize FIP

 

Development

 

 

 

Project management

  • Project milestones

  • Time estimates for reaching project milestones

 

Development

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

 

RAM bumps for new actions

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

 

Fees for new actions

https://fioprotocol.atlassian.net/browse/BD-3829

Update FIP (or development document)

https://fioprotocol.atlassian.net/browse/BD-4276

ABI validation

https://fioprotocol.atlassian.net/browse/BD-4157

Code review

FIO does DAC-style code reviews wherein the following core team members are required to review all major PRs:

  • Core developers - Full review

  • Security - Full review. TBD on how this will be handled.

  • QA and Release Management- Summary review to acknowledge understanding that the feature is in development

If a developer approves a PR, it is assumed that they have taken the time to do a thorough review. Just checking the box is inadequate and puts the chain at risk. If a bug or structural issue escapes, we will be taking joint responsibility for not finding it during our reviews. If a developer wants to dig deeper and has questions for the main developer, they should initiate a discussion with the developer.

https://fioprotocol.atlassian.net/browse/BD-4156

Unit Testing

 

 

 

Action and getter testing

This feature was handed to QA for testing. No initial tests created.

Performance testing

 

Release Plan

 

 

 

Msig deployment

Example: [fio 3.3 fio.contracts 2.7] Release script

Done: https://fioprotocol.atlassian.net/wiki/spaces/FD/pages/553451527

QA

 

 

 

Handoff to QA

https://fioprotocol.atlassian.net/browse/BD-3731

UAT

 

 

 

Merge to develop and install on DEV

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.

This should be a release or PM task.

Feature complete

 

Devnet

 

 

 

Devnet testing

Devnet testing is tracked in the Release Milestone Checklist

Testnet

 

 

 

Test planning

Includes:

  • New actions (addaction)

  • New fees (createfee)

  • List of contracts modified

https://fioprotocol.atlassian.net/browse/BD-4277

Testnet rollout verification

 

Mainnet

 

 

 

Test planning

See Release Milestone Checklist

Mainnet rollout verification