[FIP-43] Development Milestone Checklist

Owned by Eric Butz
Last updated: Nov 17, 2022
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

 

 

 

Dev Epic or Story

 

Project manager will create initial Epic or Story

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

FIP Wiki

 

Project manager will create FIP Wiki

[FIP-43] Update get_fee validation

Development Stories

 

Subtasks/stories created for items in the Development Milestone Checklist

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

Github repo

 

Create bug/feature branch

See: FIO Protocol Developer Hub

 

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

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: FIO Protocol Developer Hub

 

RAM bumps for new actions

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

 

Fees for new actions

 

Update FIP (or development document)

 

ABI validation

 

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-4186

Unit Testing

 

 

 

Action and getter testing

QA will create tests.

Performance testing

 

Release Plan

 

 

 

Msig deployment

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

 

QA

 

 

 

Handoff to QA

Simple update. No formal handoff required.

Devnet

 

 

 

Devnet testing

No new endpoints or actions

Testnet

 

 

 

Test planning

No new endpoints or actions

Testnet rollout verification

No new endpoints or actions

Mainnet

 

 

 

Test planning

No new endpoints or actions

Mainnet rollout verification

No new endpoints or actions