Versions Compared

Old Version 3

changes.mady.by.user Michael Leet

Saved on

compared with

New Version Current

changes.mady.by.user Eric Butz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The milestone checklist tracks the development tasks that need to be completed for releases.

Task

Deliverables

Notes

Kickoff

Master Release Schedule

  •  Master release schedule updated with release

Project wiki

  •  Project wiki created for release

Epic

  •  Epics created for release (including PM, RM, and QA)

Project Management Stories

  •  Stories created for items in the Release PM Milestone Checklist

Update Dashboard

  •  Update release dashboard

Meeting - Release kickoff meeting

  •  Kickoff meeting held with team to review release

Security

See description

Code audit

  •  Excluded
  •  Included
  •  Code audit of new contract or code

Vulnerability testing

  •  Excluded
  •  Included
  •  Penetration, API, and logic vulnerability testing

Bug bounty

  •  Excluded
  •  Included
  •  Bug bounty

SDKs

  •  Excluded
  •  Included

See description

SDKs

  •  Epic created to track SDK Release

SDK dev complete

  •  SDK development complete for all features in release

Release Plan

Rollout planning

  •  Work with release manager on rollout plan

Testnet

Test planning

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

See Release Milestone Checklist

Testnet rollout verification

  •  Work with release manager to perform the Testnet rollout verification for the feature and report findings (add results to Dev Spec)

SDK Release

  •  Confirm develop branch has all updates for new release
  •  Create “vn.n.n-rc1” tag

This may be a release management task.

Mainnet

Test planning

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

See Release Milestone Checklist

Mainnet rollout verification

  •  Work with release manager to perform the Mainnet rollout verification for the feature and report findings (add results to Dev Spec)

Post-deployment

FIP status

  •  Move FIP status to Final and include release links; update master README index

Devhub

fiosdk_typescript-examples

Partner upgrades

  •  Create upgrade blog post and send to Account Management team to manage upgrades
  •  Work with Account Management to coordinate Mainnet rollout plan with the BP, wallet, and exchange community, watch over the execution and help to ensure rollout is completed in full.

Security

Background – The security of the FIO protocol against DDOS and man in the middle attacks is one of the primary security objectives of the prorftol. The FIO protocol also concerns itself with the many ways that users might attempt to game the provided interfaces in order to gain FIO or to impede the experience of other users.

...

Bug Bounty – Your project may benefit from placing a bounty on the contract modifications. Your project should consider offering a reward if any community member is able to discover security flaws, or vulnerabilities in new features. These bounties may be long lived, and they may require the use of private test instances of the fio test net to provide hackers ample opportunity to “break the chain”.

SDKs

Background – Changes to Kotlin, javascript, and Golang SDKs may be necessary for each release of the FIO protocol. SDK changes should go through a QA process. The release manager must integrate the SDK changes required for a release, then perform acceptance tests on these changes.

...