You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by Alan Gates <al...@gmail.com> on 2015/02/19 19:56:03 UTC
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 when we actually release this in a version we can update all the
JIRAs with that label.
Alan.
Re: Fix version for hbase-metastore branch
Posted by Thejas Nair <th...@gmail.com>.
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 <th...@gmail.com> 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.
>
>
> On Thu, Feb 19, 2015 at 10:56 AM, Alan Gates <al...@gmail.com> wrote:
>
>> 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.
>>
>
>
Re: Fix version for hbase-metastore branch
Posted by Thejas Nair <th...@gmail.com>.
Done.
On Thu, Feb 19, 2015 at 7:12 PM, Alan Gates <al...@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 <ha...@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 <th...@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 <al...@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.
>
>
Re: Fix version for hbase-metastore branch
Posted by Lefty Leverenz <le...@gmail.com>.
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 <al...@gmail.com> wrote:
> 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 <le...@gmail.com>
> February 19, 2015 at 23:01
> 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
>
>
> Alan Gates <al...@gmail.com>
> February 19, 2015 at 19:12
> 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 <ha...@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 <th...@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 <al...@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.
>
>
Re: Fix version for hbase-metastore branch
Posted by Alan Gates <al...@gmail.com>.
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 <ma...@gmail.com>
> February 19, 2015 at 23:01
> 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
>
>
> Alan Gates <ma...@gmail.com>
> February 19, 2015 at 19:12
> 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 <ma...@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 <ma...@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 <ma...@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.
Re: Fix version for hbase-metastore branch
Posted by Thejas Nair <th...@gmail.com>.
TODOC-HBMETA sounds good to me.
On Thu, Feb 19, 2015 at 11:01 PM, Lefty Leverenz <le...@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 <al...@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 <ha...@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 <th...@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 <al...@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.
>>
>>
>
Re: Fix version for hbase-metastore branch
Posted by Lefty Leverenz <le...@gmail.com>.
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 <al...@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 <ha...@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 <th...@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 <al...@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.
>
>
Re: Fix version for hbase-metastore branch
Posted by Alan Gates <al...@gmail.com>.
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 <ma...@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 <ma...@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 <ma...@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.
Re: Fix version for hbase-metastore branch
Posted by Ashutosh Chauhan <ha...@apache.org>.
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 <th...@gmail.com> 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.
>
>
> On Thu, Feb 19, 2015 at 10:56 AM, Alan Gates <al...@gmail.com> wrote:
>
> > 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.
> >
>
Re: Fix version for hbase-metastore branch
Posted by Thejas Nair <th...@gmail.com>.
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 <al...@gmail.com> wrote:
> 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.
>