No the RM will move the fix version. This is just me requesting that you flush your work if you have something pending.
On Fri, Oct 4, 2019 at 3:19 PM Sakthi <[email protected]> wrote: > Do RMs need to send out an email saying they are planning to cut out an RC > soon so people need to tag any new upcoming jiras with the next version > (which the RM might have already created?). For 1.3.6 I was blocked on the > canary change. Meanwhile HBASE-23116 > <https://issues.apache.org/jira/browse/HBASE-23116> popped up. Because it > was just logging change I didn't mind excluding it from the RC. So I had > bumped up the version to 1.3.7. I was thinking what could be a more cleaner > way of communication? > > On Fri, Oct 4, 2019 at 2:42 PM Andrew Purtell <[email protected]> wrote: > > > Just to be clear, the commits arent' the issue, backports aren't the > issue, > > coordination with the RM is the issue. > > > > On Fri, Oct 4, 2019 at 2:38 PM Andrew Purtell <[email protected]> > wrote: > > > > > Got blocked on a couple of half done commits in progress when trying to > > > spin the 1.5.0 RC this afternoon. > > > > > > Going forward we have to be better about this. > > > > > > -- > > > Best regards, > > > Andrew > > > > > > Words like orphans lost among the crosstalk, meaning torn from truth's > > > decrepit hands > > > - A23, Crosstalk > > > > > > > > > -- > > Best regards, > > Andrew > > > > Words like orphans lost among the crosstalk, meaning torn from truth's > > decrepit hands > > - A23, Crosstalk > > > -- Best regards, Andrew Words like orphans lost among the crosstalk, meaning torn from truth's decrepit hands - A23, Crosstalk
