Differences

This shows you the differences between two versions of the page.

Link to this comparison view

processes:network_upgrades:code_considerations [2026/07/23 12:13] – created blackwolfsaprocesses:network_upgrades:code_considerations [2026/07/23 12:13] (current) – blackwolfsa
Line 1: Line 1:
-When doing network upgrades, and fixes, we need to if a particular fix is applicable enough for an exchange or pool operators. if it is, we need to contact them of the required version. We send the a message containg the reason for the upgrade and version they need to upgrade to. Version details on github should contain all required information for upgrading.  +When doing network upgrades and fixes, we need to assess whether a particular fix is relevant to exchange or pool operators. If it is, we need to notify them of the required version. We send them a message containing the reason for the upgrade and the version they need to upgrade to. The version details on GitHub should contain all the information required for upgrading.
-When a release contains a critical hidden security vulnerability, we give two weeks' private notice about the fix and why it's required before we publicly anounce the bug and fix.  +
-When the release contains a hardfork that contains network consensus changes we need to give a X months notice to ensure every node is upgraded by the time the fork block height it reached. +
  
 +When a release contains a critical undisclosed security vulnerability, we give two weeks' private notice about the fix and why it's required before we publicly announce the bug and the fix.
 +
 +When a release contains a hard fork with network consensus changes, we need to give 2 months' notice to ensure every node is upgraded by the time the fork block height is reached.