[FIP-39] Milestone Checklist

Subject

Owner

Description

Jira Links and Notes

Subject

Owner

Description

Jira Links and Notes

Definition

 

 

 

Create initial Epic or Story

PM

Create initial Epic or Story

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

Create FIP Wiki

PM

Create FIP Wiki

[FIP-39] testing and release

Create stories and subtasks

PM

Subtasks/stories created for items in the Development Milestone Checklist

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

Requirements and Scoping

 

 

 

FIP-NN Requirements - Project kickoff

PM

Kickoff meeting held with Product Manager to review requirements

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

FIP-NN Requirements - Complete FIP

PM

FIP reviewed and moved to Accepted status

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

FIP-NN Master release schedule

PM

Update master release schedule with feature actions and endpoints

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

Design and Scoping

 

 

 

FIP-NN Requirements - Functional / Technical design

Dev

Complete technical design and save to wiki. Design draft should include a first draft of all elements outlined in the Development Spec.

Template: [FIP-nn] Development - Spec

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

FIP-NN Estimate stories

Dev

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.

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

FIP-NN Design review

Dev

Functional spec approved by architecture champions and team

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

FIP-NN Design - Update FIP

Dev

Update FIP with any changes resulting from design review

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

Development

 

 

 

FIP-NN Complete development

Dev

Complete all development for feature. This may include multiple stories and subtasks for larger features. Include link to PR in story.

Includes

  • Create bug/feature branch and draft PR for new feature (e.g., feature/fip-16-lock-tokens, See: https://developers.fioprotocol.io/docs/developers/git )

  • Create fio.devtools branch and draft PR for new feature (e.g., feature/fip-16-lock-tokens). Add new fees and actions, etc.

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

FIP-NN Ram bump analysis

Dev

Determine RAM allocation for new actions and set RAM bump accordingly. This information should be added to the FIP.

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

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

FIP-NN Fee analysis

Dev

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

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

FIP-NN ABI Validation

Dev

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

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

FIP-NN Dev - Update FIP and development spec

Dev

Update the FIP and development spec to make sure they are aligned with the latest code. This includes making sure the error messages are the same between the code and the FIP.

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

FIP-NN Code review

Dev

Code review of PR from all core devs, release management, and QA

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

FIP-NN Deployment release guide

Dev

Create deployment release guide. This is used by release management to define needed msigs during testnet and mainnet deployments

Includes:

  • New actions (addaction)

  • New fees (createfee)

  • List of contracts modified

Template: [FIP-nn] Deployment and rollout guide

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

Unit Testing

 

 

 

FIP-NN Unit testing - Action and getter unit tests

Dev

Includes initial development of unit tests for handoff to QA:

  • Create fio.test branch and draft PR for initial unit tests created on fio.test (e.g., feature/fip-16-lock-tokens)

  • Development of initial action and getter unit tests

  • Tests run cleanly

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

FIP-NN Unit testing - Performance tests

Dev

Create first level performance testing results reviewed with architecture champions (can be performed on dev machine, try to uncover any obvious perf limits)

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

FIP-NN Dev - Test guide

Dev

Add testing info to this story for QA. This is a brainstorming list of items from the developer to make sure specific items are tested. Includes:

  • Note any areas of existing code that are impacted by the new feature and should be tested as part of this feature testing

  • Any use cases that need to be included

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

FIP-NN Dev - QA handoff

Dev

Review code and unit tests with QA and Release Management.

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

SDKs

 

 

 

FIP-NN SDK updates

PM

Create epic/stories to track SDK Release (if changes are needed for new features)

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

QA

 

 

 

FIP-NN QA - Create Test Cases

QA

List out all the test cases in a subtask attached to the QA story

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

FIP-NN QA - Test plan review

QA

Meeting held with Dev Manager and Lead Dev to review test plan

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

FIP-NN QA - Feature Testing

QA

Complete feature testing, including:

  • fio.test enhanced with functional tests

  • Tests run cleanly

  • Functional tests well documented (in fio.test) and reviewed with team

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

FIP-NN QA - Performance testing

QA

Complete performance testing, including:

  • Work with Dev Lead to create performance test plan

  • fio.test enhanced with performance tests

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

FIP-NN QA - History node testing

QA

Test against node with V1 History and confirm no errors in log file (add results to Dev Spec)

For transactions that automatically create accounts (e.g., regdomain) if the public key used is new, we need to make sure that the correct entries are added to the the history_plugin.cpp. See for example: https://github.com/fioprotocol/fio/pull/363/files

To test, the transaction should be run, and a history get_actions for the target account should show the (regdomain, etc.) action.

When released to testnet, it should be confirmed that http://bloks.io shows the appropriate transaction history.

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

FIP-NN QA - Test review

QA

System and performance tests and results reviewed with Dev team

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

UAT

 

 

 

FIP-NN UAT - Install release on DEV server

PM

Install release on DEV server. This is a 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.

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

FIP-NN UAT - System testing

QA

Complete system testing, including:

  • All bugs and outstanding items completed

  • JS tests completed and run cleanly against DEV server

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

FIP-NN UAT - Confirm feature and QA complete

PM

Confirm all bugs and outstanding items completed

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

FIP-NN UAT - Product Management signoff

PM

Get signoff from Product Management

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

Testnet

 

 

 

FIP-NN Testnet rollout verification

PM

With developer, perform the Testnet rollout verification for the feature and report findings in story

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

Mainnet

 

 

 

FIP-NN Mainnet rollout verification

PM

With developer, perform the Testnet rollout verification for the feature and report findings in story

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