TODOC-HBMETA sounds good to me.
On Thu, Feb 19, 2015 at 11:01 PM, Lefty Leverenz <leftylever...@gmail.com> wrote: > Also, what should we use for a documentation label? (HIVE-9606 > <https://issues.apache.org/jira/browse/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 hbase-metastore branch? Maybe TODOC-HBMETA? > > -- Lefty > > On Thu, Feb 19, 2015 at 7:12 PM, Alan Gates <alanfga...@gmail.com> 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 <hashut...@apache.org> >> February 19, 2015 at 11:22 >> This is what we have been doing for cbo work. e.g. >> https://issues.apache.org/jira/browse/HIVE-9581 >> >> >> Thejas Nair <thejas.n...@gmail.com> >> February 19, 2015 at 11:17 >> 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. >> >> >> >> Alan Gates <alanfga...@gmail.com> >> February 19, 2015 at 10:56 >> 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 >> when we actually release this in a version we can update all the JIRAs with >> that label. >> >> Alan. >> >> >
