The Bravo/Bahamas release includes features that add new tables and require table migrations. The updates that drive these migrations span several contract deployments and the full cycle must be tested in Devnet.
...
fio - release/2.0.x-dev
fio.contracts - release/2.2.x
fio.test - release/2.2.x
fio.devtools - develop
Base Test
Run fio.test release/2.2.x
Bravo update (fio.contracts Step 1)
Update all nodes to fio.contracts Bravodevelop
Run JS testsfio.test project/bravo
Run FIP-1.b migration scripts
Run FIP-1.b migration confirmation scripts
Run JS test
FIP-1.a table migration step 1 testing
Running migration test script
Run JS regression tests.fio.test project/bravo
Bahamas (fio) update
Fork testing
Ensure nodes are launching with History
Update 6 nodes to fio Bahamas and ensure no forking occurs
Run table migration test against both types of nodes (see below)
Update 15 nodes to fio Bahamas and ensure no forking occurs
Do NOT update remaining nodes to Bahamas
Run FIP-1.b migration confirmation scripts
Run JS regression tests against upgraded nodes.
Run JS regression tests against non-upgraded nodes.
FIP-1.a table migration testing
Use the same Request and OBT records to test FIO Request and OBT against a node on 2.0.0 and a node on Bahamas.
Delta update (fio.contracts Step 2)
...