Re: Fix version for hbase-metastore branch

D'oh! I'd forgotted about the idea of a doc JIRA. In that case, we don't really need the label. (Less clutter in the label drop-down.) -- Lefty On Fri, Feb 20, 2015 at 8:38 AM, Alan Gates wrote: > TODOC-HBMETA works for me. I'll change that at the same time I fix the > change versions. I'l

Re: Fix version for hbase-metastore branch

TODOC-HBMETA works for me. I'll change that at the same time I fix the change versions. I'll also open a JIRA for docs on this stuff with links to the JIRAs that need documentation. Alan. Lefty Leverenz February 19, 2015 at 23:01 Also, what should we use for

Re: Fix version for hbase-metastore branch

TODOC-HBMETA sounds good to me. On Thu, Feb 19, 2015 at 11:01 PM, Lefty Leverenz wrote: > Also, what should we use for a documentation label? (HIVE-9606 > needs one.) > > TODOC labels are proliferating for all the releases and branches, but I

Re: Fix version for hbase-metastore branch

Done. On Thu, Feb 19, 2015 at 7:12 PM, Alan Gates wrote: > Could someone with admin permissions on our JIRA add an > hbase-metastore-branch label? I'll take care of changing all the fix > versions for the few JIRA's we've already committed. Thanks. > > Alan. > > Ashutosh Chauhan > Februar

Re: Fix version for hbase-metastore branch

Also, what should we use for a documentation label? (HIVE-9606 needs one.) TODOC labels are proliferating for all the releases and branches, but I don't think a generic TODOC label would be helpful. So what would be a good abbreviation for the hb

Re: Fix version for hbase-metastore branch

Could someone with admin permissions on our JIRA add an hbase-metastore-branch label? I'll take care of changing all the fix versions for the few JIRA's we've already committed. Thanks. Alan. Ashutosh Chauhan February 19, 2015 at 11:22 This is what we have been

Re: Fix version for hbase-metastore branch

This is what we have been doing for cbo work. e.g. https://issues.apache.org/jira/browse/HIVE-9581 On Thu, Feb 19, 2015 at 11:17 AM, Thejas Nair wrote: > I agree, using a label for fix version makes sense in this case. I believe > that is what had been done for hive-on-spark and hive-on-tez. > >

Re: Fix version for hbase-metastore branch

Looks like hive-on-tez and hive-on-spark didn't update the fix version after merge to trunk. But I think updating the fix version after merge makes sense. On Thu, Feb 19, 2015 at 11:17 AM, Thejas Nair wrote: > I agree, using a label for fix version makes sense in this case. I believe > that is

Re: Fix version for hbase-metastore branch

I agree, using a label for fix version makes sense in this case. I believe that is what had been done for hive-on-spark and hive-on-tez. On Thu, Feb 19, 2015 at 10:56 AM, Alan Gates wrote: > I've been marking JIRAs on this branch as fixed in 1.2, since that's the > next version. But that seems

Fix version for hbase-metastore branch

I've been marking JIRAs on this branch as fixed in 1.2, since that's the next version. But that seems wrong as I doubt this code will be in by 1.2. What's the usual practice here? It seems it would make sense to make a label for this branch and mark them as fixed with that label and then whe