the chaincode becomes active on a channel. More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to change additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.x are supported, so that network components can be upgraded one at a time with no downtime. The upgrade docs have

chaincode becomes active on a channel. • More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. • Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.x are supported, so that network components can be upgraded one at a time with no downtime. The upgrade docs have

the chaincode becomes active on a channel. More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to change additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.x are supported, so that network components can be upgraded one at a time with no downtime. The upgrade docs have

chaincode becomes active on a channel. • More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. • Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.x are supported, so that network components can be upgraded one at a time with no downtime. The upgrade docs have

the chaincode becomes active on a channel. More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to change additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.0 are supported, so that network components can be upgraded one at a time with no downtime. The upgrade docs have

chaincode becomes active on a channel. • More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. • Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.0 are supported, so that network components can be upgraded one at a time with no downtime. The upgrade docs have

the chaincode becomes active on a channel. More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to change additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.0 are supported, so that network components can be upgraded one at a time with no downtime. The upgrade docs have

smart contracts, and new options for operating nodes. What has stayed the same is the ability to upgrade network components on your own terms, with support for rolling upgrades from v1.4.x, and the ability the chaincode becomes active on a channel. More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to change

smart contracts, and new options for operating nodes. What has stayed the same is the ability to upgrade network components on your own terms, with support for rolling upgrades from v1.4.x, and the ability chaincode becomes active on a channel. • More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. • Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to

chaincode becomes active on a channel. • More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. • Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.0 are supported, so that network components can be upgraded one at a time with no downtime. The upgrade docs have