Thanks! I have closed all the issues that were updated to 2.0 since yesterday. Can you bulk close any other issues if adding them to 2.0, after setting the version?
On 16/2/17, 06:08, "Xuefu Zhang" <xzh...@cloudera.com> wrote: >I don't think 2.0 branch has every patch from spark-branch. However, >master >does. I will take care of spark branch JIrA resolution versions. > >Thanks, >Xuefu > >On Tue, Feb 16, 2016 at 9:48 PM, Thejas Nair <thejas.n...@gmail.com> >wrote: > >> The hbase-metastore branch jiras are all part of Hive 2.0.0 release, >> as no work was done in that branch after the merge into the master >> branch. >> I think we should add 2.0.0 as a fix version before closing them. >> Thoughts ? >> >> I am not sure if that is the case with spark-branch. Ideally, I think >> we should update the fix version whenever we merge the branch into >> master/branch-1 . >> >> >> >> On Tue, Feb 16, 2016 at 5:31 PM, Sergey Shelukhin >> <ser...@hortonworks.com> wrote: >> > Hi. >> > There is a number of JIRAs resolved in a variety of branches that are >>a >> > part of 2.0 release. >> > We need to close these; I’ll take care of closing the llap JIRAs; as >>far >> > as hbase-metastore-branch and spark-branch are concerned, any >>objection >> to >> > closing these? None of them look new. I will close tomorrow if no >> > objections. >> > >> > >> >>https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20% >>28 >> > >> >>fixVersion%20%3D%20spark-branch%20OR%20fixVersion%20%3D%20hbase-metastore >>-b >> > >> >>ranch%29%20AND%20fixVersion%20not%20in%20%282.0.0%2C%202.1.0%29%20AND%20s >>ta >> > >>tus%20%3D%20Resolved%20ORDER%20BY%20fixVersion%20ASC%2C%20resolved%20DESC >> > >>
