processes:network_upgrades:code_considerations

**This is an old revision of the document!**

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 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.

processes/network_upgrades/code_considerations.1784808785.txt.gz · Last modified: 2026/07/23 12:13
CC Attribution-Share Alike 4.0 International Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International