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
Deploying FIO Contracts (fioprotocol.io)
Tasks
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
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.
...
*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. This environment is primarily used for fork testing (see Devnet Testing (fioprotocol.io)), although contract testing may be performed as well. Keep in mind that testing here may be costly as there are 4 distributed nodes running 21 BPs.
LocalNet, while not an environment persay, is used by all developers to develop, build, deploy and test updates, driven by FIPs or Hotfixes. It is the concept of building, deploying and testing locally. It may consist of entirely local processing, i.e. run the server then run fio.test pointing to localhost, or the use of virtual machines or the use of one’s own machine testing against an AWS instance.
Release Content
The Project Manager will provide details and links to Development Documents, Development Documents (Active), to be included in a release.
...
The release branch naming will looking follow the release as naming conventions outlined in Git Branching and Release Strategy. See the current releases documented in Releases folder.
...