Thanks for pointing out this, Ruben. I also have this question. But in our scrum, we can merge commits to master at the moment we have a release branch.
Best, Chunwei On Wed, Feb 26, 2020 at 8:52 PM Ruben Q L <rube...@gmail.com> wrote: > Hello everyone, > > as you know, we are in the middle of the release process for 1.22 (btw, > thanks Danny for your effort as release manager). > However, if I am not mistaken I can see that some PRs have been merged > during this time, at least [1] and [2]. I am wondering if during this > process (from the build of the first release candidate to the final > approval of the release), we should not be in some kind of "code freeze", > where commits are not allowed, unless they are explicitly approved > (ultimately by the release manager, I guess) in order to solve issues with > the release candidates (e.g. [3]). Is there any rule / guideline about > this? > > Best regards, > Ruben. > > [1] https://issues.apache.org/jira/browse/CALCITE-3817 > [2] https://issues.apache.org/jira/browse/CALCITE-3734 > < > https://slack-redir.net/link?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FCALCITE-3734&v=3 > > > [3] https://issues.apache.org/jira/browse/CALCITE-3822 >
