Hi Tomas, Tomas Volf <[email protected]> writes:
[...] >> Having a distinct release branch would avoid the extra communication >> needed here and prevent the unavoidable mistakes. > > Would this not turn the release branch into an endless Whac-A-Mole of > trying to fix stuff? My impression of current state of CI and QA in > Guix is — and please correct me if I am wrong — that we cannot really > ensure that "new" stuff does not break something. For example system > tests are not even a part of the CI. So the release branch would get > into working order, the release team would rebase on current master, and > it would be (possibly) broken again. > > Am I overlooking something? The release branch wouldn't sync with master until the release is tagged and done. It could cherry-pick some commits that would fix test issues for example or other bug fixes from master, but it wouldn't be rebased as that would defeat having a distinct, isolated branch to prep the release. -- Thanks, Maxim
