Hi all, in the past many RCs had to be cancelled probably because cutting a release is sort happening by taking a snapshot at a given time and instantly trying to release it.
Given the amount of commits I see in this project every day, perhaps it would make sense to announce the next release process being started at a given date & time and to cut a release branch on that date. This way anyone has the chance to finish features that should go in this release … on the release branch we can then test and check that everything’s fine and works as expected. As soon as the release branch is stable, that’s released. In the code-stabilization phase I would suggest to no include any new features or improvement … just fixes for problems that are found. This way the project can continue development without any issues and we can stabilize the release before cutting the RC. Perhaps this way we can reduce the amount of cancelled RCs The main problem I see here, is that for example I have stopped doing early RC validation for IoTDB as in the past a lot of RCs I invested time in reviewing were cancelled and updated with a big number of changes, which forced me to do my review in full extent again. This sort of made me more cautious and so now I wait 2-3 days before starting to do it. Just my thoughts … Chris
