This will require an adjustment of rewards script:
The discussed rewards script adjustment will allow us to release small improvements/patches for tBTC beta operators quickly and often. Patches are denoted by the last digit of the version tag: v.2.0.1, v2.0.2, v.2.0.3 and so on. This is especially important in the context tBTC load surge we observe in the recent days. We need a quick release process to act quickly in case of problems. Nothing changes for the rest of the network - they will receive rewards if they are on the latest minor version so v2.0.x, v2.1.x, v2.2.x and so on (regardless of how many patches x was released for the given minor version)
Up to now the version strategy for tBTC consists of releasing new versions with a
-mXsuffix:v2.0.0-m1,v2.0.0-m2,v2.0.0-m3, and so on.The new version strategy uses semantic versioning https://semver.org/.
This will require an adjustment of rewards script: