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 Next »

While the checklists capture the ToDos for a release, the following notes address the what and how of a release from localnet to mainnet.

References:

Git Branching and Release (fioprotocol.io)

Release Management Checklist Template

LocalNet: FIO LocalNet Release Notes

Devnet: FIO DevNet Release Notes

TestNet:

Overview/Notes

Release Management focuses on the capture (release branching) and delivery (deployment and test to *DevNet, TestNet, MainNet) of features, bugs, etc.

MainNet deliveries: most changes will be merged into the Develop branch and flow down through DevNet, and TestNet but some (Hot Fixes) may not.

*DevNet deployment/test is considered happy path deployment and testing. It may be prudent to smoketest FIP branches (to be/are merged into Develop) to verify a Develop branch.

Release Content

The Project Manager will provide details and links to Development Documents, Development Documents (Active), to be included in a release.

Release Branching

The release branch naming will looking follow the release as documented in Releases folder.

Release Readiness

Release readiness entails the process of gathering the information noted above but also the deployment and testing of FIP, Develop branches along with application of the Release script on these branches to identify any issues, gaps in functionality, prior to cutting a release branch. This could include a formal review/demo of the Feature(s) with the Project Manager and the team.

  • No labels