> 4. During an RC vote, new blockers may still be raised if they are confirmed > regressions.
I will take issue with this if it is interpreted as "if and only if they are confirmed regressions." Sufficiently significant issues should always be capable of blocking a release regardless of whether or not they are strictly regressions. Of course, there are judgements to be made as to whether an issue is "sufficiently significant" and therefore is actually a blocker. An issue being a regression is one good indication that it is a blocker, but it is not the only one, and an issue not being a regression should not always exclude it from being a blocker. For example, if a significant security issue is discovered during a release process, that release train should halt until we have a fix for the issue or some other compromise has been thoroughly discussed and voted on. Similarly, other claimed blockers should get at least some acknowledgement, discussion and evaluation, not just a curt dismissal along the lines of "it's not a regression, therefore we are moving on." --------------------------------------------------------------------- To unsubscribe e-mail: [email protected]
