tbh the RM can make this call. Whether or not 1 week is aggressive, really depends on the scope of release, whats left to land/test.
Would it be useful to frame the discussion in that way? On Mon, Sep 19, 2022 at 1:25 PM zhaojing yu <maidou...@gmail.com> wrote: > Do anyone else have any suggestions? > We will determine the time of the code freeze tomorrow. > > Sivabalan <n.siv...@gmail.com> 于2022年9月19日周一 14:05写道： > > > Hey hi Zhaojing, > > Announcing a code freeze just 1 week ahead might be too aggressive. > > Do you think, we can make it sometime next week(week of 26th) to give > some > > buffer for folks to push any critical fixes in. Open to hear what others > > have to say. > > > > > > > > On Fri, 16 Sept 2022 at 01:47, zhaojing yu <maidou...@gmail.com> wrote: > > > > > To clarify, 09/21 is to cut RC1 and it will be released if all > > > testing/checks pass. > > > > > > zhaojing yu <maidou...@gmail.com> 于2022年9月16日周五 16:45写道： > > > > > > > Hi folks, > > > > > > > > As the RM for the 0.12.1 release, I'd like to propose the code freeze > > on > > > > Sep 21 (Wed) for any bug fixes that are going to be included in the > > minor > > > > release, about a month after the 0.12.0 release. Let me know if you > > need > > > > more time for fixing any issues. > > > > > > > > Please tag any fix that you think we should include in 0.12.1, by > > setting > > > > the "Fix Version/s" to "0.12.1" in the corresponding Jira ticket. As > > the > > > > RM, I will make the final decision. I have started cherry-picking > the > > > > commits from the master. I will watch out for ongoing critical fixes > > and > > > > remind authors and reviewers in the PRs along the way so they can > land > > in > > > > time. > > > > > > > > cherry-picking link： > > > > > > > > > > https://docs.google.com/document/d/1G4eeZkSUqMgONRI2YE0o_XBxy9kBaq_Cznolfp2VhS8/edit#heading=h.3fl3egu0kv0z > > > > > > > > Thanks, > > > > - Zhaojing > > > > > > > > > > > > > -- > > Regards, > > -Sivabalan > > >
