You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by Josh Elser <jo...@gmail.com> on 2016/08/02 15:28:02 UTC
Re: new 4.8.0 RC?
Shouldn't we bump the 4.x and master branch to 4.9.0-HBase**-SNAPSHOT? I
just noticed that we have the same Maven versions on both the 4.8 and
4.x branch sets.
Ankit Singhal wrote:
> Following 4 branches have been created and are now available for commits
> targeted for 4.8.0 only.
>
> 4.8-HBase-0.98 (from 4.x-HBase-0.98)
> 4.8-HBase-1.0 (from 4.x-HBase-1.0)
> 4.8-HBase-1.1 (from 4.x-HBase-1.1)
> 4.8-HBase-1.2 (from master)
>
> Any commit targeted for 4.8.1 or 4.9+ along with 4.8.0 can go in master and
> 4.x branches now.
>
> Regards,
> Ankit Singhal
>
> On Thu, Jul 28, 2016 at 4:25 PM, Ankit Singhal<an...@gmail.com>
> wrote:
>
>> Ok, Given that 4.8.0 RC is taking time , we can fork 4.8-HBase-x.y
>> branches so that new features and bugs target for future releases(4.9+) can
>> be committed in 4.x branches and master.
>>
>> Whatever is targeted for 4.8.0 needs to be committed in all 8
>> branches(three 4.x branches , master, four 4.8-HBase-x.y) as all 4.8
>> releases(including 4.8.0 or 4.8.x) will be done from 4.8-HBase-x.y branches.
>>
>> I'll create the following new branches tomorrow morning IST,
>> 4.8-HBase-0.98 (from 4.x-HBase-0.98)
>> 4.8-HBase-1.0 (from 4.x-HBase-1.0)
>> 4.8-HBase-1.1 (from 4.x-HBase-1.1)
>> 4.8-HBase-1.2 (from master)
>>
>> Let's discuss if someone has any concerns.
>>
>> Regards,
>> Ankit Singhal
>>
>> On Sun, Jul 24, 2016 at 2:19 PM,<la...@apache.org> wrote:
>>
>>> Also, can we branch 4.8-x in git?That way bigger changes can still go
>>> into the 4.x branches, while bugs are fixed in 4.8-x branches.
>>> -- Lars
>>>
>>> From: James Taylor<ja...@apache.org>
>>> To: "dev@phoenix.apache.org"<de...@phoenix.apache.org>
>>> Sent: Thursday, July 21, 2016 7:16 PM
>>> Subject: new 4.8.0 RC?
>>>
>>> How about a cutting a new RC now that the licensing work is complete,
>>> Ankit? Looks like we can simplify the voting too by just having a single
>>> vote across all versions by just include all the information in one VOTE
>>> thread.
>>>
>>> Would be good to get PHOENIX-3078 in too, if possible. We've had a few
>>> other fixes come in which IMHO are all ok to include in the new RC.
>>>
>>> Thanks,
>>> James
>>>
>>>
>>>
>>>
>>
>
Re: new 4.8.0 RC?
Posted by la...@apache.org.
What I do to allow commit even while running the tests is to create a tag in tag and then run jenkins against that tag instead of a branch.
-- Lars
From: Ankit Singhal <an...@gmail.com>
To: dev@phoenix.apache.org
Sent: Wednesday, August 3, 2016 1:35 AM
Subject: Re: new 4.8.0 RC?
Yeah. Let's cut RC from 4.x only as there is not much difference except
PHOENIX-3138, PHOENIX-3128,PHOENIX-3120. Which I think are fine for 4.8.0
too
I'm running some tests for RC so no more commit please.
On Wed, Aug 3, 2016 at 5:42 AM, James Taylor <ja...@apache.org> wrote:
> I only pushed my changes to 4.x, so please let me know if I need to push
> them to 4.8 branches, Ankit.
>
> Would be great to get an RC up today (IST time) for folks to test out
> tomorrow (US time).
>
> Thanks,
> James
>
> On Tue, Aug 2, 2016 at 4:21 PM, Josh Elser <jo...@gmail.com> wrote:
>
> > Either works for me. The two changes I'm committing today have just gone
> > to 8 branches instead of 4.
> >
> > Ankit, do you have a preference as RM what to do?
> >
> >
> > James Taylor wrote:
> >
> >> We should, but I don't think anything has been committed against the 4.x
> >> branches that doesn't belong in the release. Maybe we should just delete
> >> the 4.8 branches and recreate them once the RC is up?
> >>
> >> On Tue, Aug 2, 2016 at 8:28 AM, Josh Elser<jo...@gmail.com>
> wrote:
> >>
> >> Shouldn't we bump the 4.x and master branch to 4.9.0-HBase**-SNAPSHOT? I
> >>> just noticed that we have the same Maven versions on both the 4.8 and
> 4.x
> >>> branch sets.
> >>>
> >>>
> >>> Ankit Singhal wrote:
> >>>
> >>> Following 4 branches have been created and are now available for
> commits
> >>>> targeted for 4.8.0 only.
> >>>>
> >>>> 4.8-HBase-0.98 (from 4.x-HBase-0.98)
> >>>> 4.8-HBase-1.0 (from 4.x-HBase-1.0)
> >>>> 4.8-HBase-1.1 (from 4.x-HBase-1.1)
> >>>> 4.8-HBase-1.2 (from master)
> >>>>
> >>>> Any commit targeted for 4.8.1 or 4.9+ along with 4.8.0 can go in
> master
> >>>> and
> >>>> 4.x branches now.
> >>>>
> >>>> Regards,
> >>>> Ankit Singhal
> >>>>
> >>>> On Thu, Jul 28, 2016 at 4:25 PM, Ankit Singhal<
> ankitsinghal59@gmail.com
> >>>> >
> >>>> wrote:
> >>>>
> >>>> Ok, Given that 4.8.0 RC is taking time , we can fork 4.8-HBase-x.y
> >>>>
> >>>>> branches so that new features and bugs target for future
> releases(4.9+)
> >>>>> can
> >>>>> be committed in 4.x branches and master.
> >>>>>
> >>>>> Whatever is targeted for 4.8.0 needs to be committed in all 8
> >>>>> branches(three 4.x branches , master, four 4.8-HBase-x.y) as all 4.8
> >>>>> releases(including 4.8.0 or 4.8.x) will be done from 4.8-HBase-x.y
> >>>>> branches.
> >>>>>
> >>>>> I'll create the following new branches tomorrow morning IST,
> >>>>> 4.8-HBase-0.98 (from 4.x-HBase-0.98)
> >>>>> 4.8-HBase-1.0 (from 4.x-HBase-1.0)
> >>>>> 4.8-HBase-1.1 (from 4.x-HBase-1.1)
> >>>>> 4.8-HBase-1.2 (from master)
> >>>>>
> >>>>> Let's discuss if someone has any concerns.
> >>>>>
> >>>>> Regards,
> >>>>> Ankit Singhal
> >>>>>
> >>>>> On Sun, Jul 24, 2016 at 2:19 PM,<la...@apache.org> wrote:
> >>>>>
> >>>>> Also, can we branch 4.8-x in git?That way bigger changes can still go
> >>>>>
> >>>>>> into the 4.x branches, while bugs are fixed in 4.8-x branches.
> >>>>>> -- Lars
> >>>>>>
> >>>>>> From: James Taylor<ja...@apache.org>
> >>>>>> To: "dev@phoenix.apache.org"<de...@phoenix.apache.org>
> >>>>>> Sent: Thursday, July 21, 2016 7:16 PM
> >>>>>> Subject: new 4.8.0 RC?
> >>>>>>
> >>>>>> How about a cutting a new RC now that the licensing work is
> complete,
> >>>>>> Ankit? Looks like we can simplify the voting too by just having a
> >>>>>> single
> >>>>>> vote across all versions by just include all the information in one
> >>>>>> VOTE
> >>>>>> thread.
> >>>>>>
> >>>>>> Would be good to get PHOENIX-3078 in too, if possible. We've had a
> few
> >>>>>> other fixes come in which IMHO are all ok to include in the new RC.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> James
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>
>
Re: new 4.8.0 RC?
Posted by Ankit Singhal <an...@gmail.com>.
Yeah. Let's cut RC from 4.x only as there is not much difference except
PHOENIX-3138, PHOENIX-3128,PHOENIX-3120. Which I think are fine for 4.8.0
too
I'm running some tests for RC so no more commit please.
On Wed, Aug 3, 2016 at 5:42 AM, James Taylor <ja...@apache.org> wrote:
> I only pushed my changes to 4.x, so please let me know if I need to push
> them to 4.8 branches, Ankit.
>
> Would be great to get an RC up today (IST time) for folks to test out
> tomorrow (US time).
>
> Thanks,
> James
>
> On Tue, Aug 2, 2016 at 4:21 PM, Josh Elser <jo...@gmail.com> wrote:
>
> > Either works for me. The two changes I'm committing today have just gone
> > to 8 branches instead of 4.
> >
> > Ankit, do you have a preference as RM what to do?
> >
> >
> > James Taylor wrote:
> >
> >> We should, but I don't think anything has been committed against the 4.x
> >> branches that doesn't belong in the release. Maybe we should just delete
> >> the 4.8 branches and recreate them once the RC is up?
> >>
> >> On Tue, Aug 2, 2016 at 8:28 AM, Josh Elser<jo...@gmail.com>
> wrote:
> >>
> >> Shouldn't we bump the 4.x and master branch to 4.9.0-HBase**-SNAPSHOT? I
> >>> just noticed that we have the same Maven versions on both the 4.8 and
> 4.x
> >>> branch sets.
> >>>
> >>>
> >>> Ankit Singhal wrote:
> >>>
> >>> Following 4 branches have been created and are now available for
> commits
> >>>> targeted for 4.8.0 only.
> >>>>
> >>>> 4.8-HBase-0.98 (from 4.x-HBase-0.98)
> >>>> 4.8-HBase-1.0 (from 4.x-HBase-1.0)
> >>>> 4.8-HBase-1.1 (from 4.x-HBase-1.1)
> >>>> 4.8-HBase-1.2 (from master)
> >>>>
> >>>> Any commit targeted for 4.8.1 or 4.9+ along with 4.8.0 can go in
> master
> >>>> and
> >>>> 4.x branches now.
> >>>>
> >>>> Regards,
> >>>> Ankit Singhal
> >>>>
> >>>> On Thu, Jul 28, 2016 at 4:25 PM, Ankit Singhal<
> ankitsinghal59@gmail.com
> >>>> >
> >>>> wrote:
> >>>>
> >>>> Ok, Given that 4.8.0 RC is taking time , we can fork 4.8-HBase-x.y
> >>>>
> >>>>> branches so that new features and bugs target for future
> releases(4.9+)
> >>>>> can
> >>>>> be committed in 4.x branches and master.
> >>>>>
> >>>>> Whatever is targeted for 4.8.0 needs to be committed in all 8
> >>>>> branches(three 4.x branches , master, four 4.8-HBase-x.y) as all 4.8
> >>>>> releases(including 4.8.0 or 4.8.x) will be done from 4.8-HBase-x.y
> >>>>> branches.
> >>>>>
> >>>>> I'll create the following new branches tomorrow morning IST,
> >>>>> 4.8-HBase-0.98 (from 4.x-HBase-0.98)
> >>>>> 4.8-HBase-1.0 (from 4.x-HBase-1.0)
> >>>>> 4.8-HBase-1.1 (from 4.x-HBase-1.1)
> >>>>> 4.8-HBase-1.2 (from master)
> >>>>>
> >>>>> Let's discuss if someone has any concerns.
> >>>>>
> >>>>> Regards,
> >>>>> Ankit Singhal
> >>>>>
> >>>>> On Sun, Jul 24, 2016 at 2:19 PM,<la...@apache.org> wrote:
> >>>>>
> >>>>> Also, can we branch 4.8-x in git?That way bigger changes can still go
> >>>>>
> >>>>>> into the 4.x branches, while bugs are fixed in 4.8-x branches.
> >>>>>> -- Lars
> >>>>>>
> >>>>>> From: James Taylor<ja...@apache.org>
> >>>>>> To: "dev@phoenix.apache.org"<de...@phoenix.apache.org>
> >>>>>> Sent: Thursday, July 21, 2016 7:16 PM
> >>>>>> Subject: new 4.8.0 RC?
> >>>>>>
> >>>>>> How about a cutting a new RC now that the licensing work is
> complete,
> >>>>>> Ankit? Looks like we can simplify the voting too by just having a
> >>>>>> single
> >>>>>> vote across all versions by just include all the information in one
> >>>>>> VOTE
> >>>>>> thread.
> >>>>>>
> >>>>>> Would be good to get PHOENIX-3078 in too, if possible. We've had a
> few
> >>>>>> other fixes come in which IMHO are all ok to include in the new RC.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> James
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>
>
Re: new 4.8.0 RC?
Posted by James Taylor <ja...@apache.org>.
I only pushed my changes to 4.x, so please let me know if I need to push
them to 4.8 branches, Ankit.
Would be great to get an RC up today (IST time) for folks to test out
tomorrow (US time).
Thanks,
James
On Tue, Aug 2, 2016 at 4:21 PM, Josh Elser <jo...@gmail.com> wrote:
> Either works for me. The two changes I'm committing today have just gone
> to 8 branches instead of 4.
>
> Ankit, do you have a preference as RM what to do?
>
>
> James Taylor wrote:
>
>> We should, but I don't think anything has been committed against the 4.x
>> branches that doesn't belong in the release. Maybe we should just delete
>> the 4.8 branches and recreate them once the RC is up?
>>
>> On Tue, Aug 2, 2016 at 8:28 AM, Josh Elser<jo...@gmail.com> wrote:
>>
>> Shouldn't we bump the 4.x and master branch to 4.9.0-HBase**-SNAPSHOT? I
>>> just noticed that we have the same Maven versions on both the 4.8 and 4.x
>>> branch sets.
>>>
>>>
>>> Ankit Singhal wrote:
>>>
>>> Following 4 branches have been created and are now available for commits
>>>> targeted for 4.8.0 only.
>>>>
>>>> 4.8-HBase-0.98 (from 4.x-HBase-0.98)
>>>> 4.8-HBase-1.0 (from 4.x-HBase-1.0)
>>>> 4.8-HBase-1.1 (from 4.x-HBase-1.1)
>>>> 4.8-HBase-1.2 (from master)
>>>>
>>>> Any commit targeted for 4.8.1 or 4.9+ along with 4.8.0 can go in master
>>>> and
>>>> 4.x branches now.
>>>>
>>>> Regards,
>>>> Ankit Singhal
>>>>
>>>> On Thu, Jul 28, 2016 at 4:25 PM, Ankit Singhal<ankitsinghal59@gmail.com
>>>> >
>>>> wrote:
>>>>
>>>> Ok, Given that 4.8.0 RC is taking time , we can fork 4.8-HBase-x.y
>>>>
>>>>> branches so that new features and bugs target for future releases(4.9+)
>>>>> can
>>>>> be committed in 4.x branches and master.
>>>>>
>>>>> Whatever is targeted for 4.8.0 needs to be committed in all 8
>>>>> branches(three 4.x branches , master, four 4.8-HBase-x.y) as all 4.8
>>>>> releases(including 4.8.0 or 4.8.x) will be done from 4.8-HBase-x.y
>>>>> branches.
>>>>>
>>>>> I'll create the following new branches tomorrow morning IST,
>>>>> 4.8-HBase-0.98 (from 4.x-HBase-0.98)
>>>>> 4.8-HBase-1.0 (from 4.x-HBase-1.0)
>>>>> 4.8-HBase-1.1 (from 4.x-HBase-1.1)
>>>>> 4.8-HBase-1.2 (from master)
>>>>>
>>>>> Let's discuss if someone has any concerns.
>>>>>
>>>>> Regards,
>>>>> Ankit Singhal
>>>>>
>>>>> On Sun, Jul 24, 2016 at 2:19 PM,<la...@apache.org> wrote:
>>>>>
>>>>> Also, can we branch 4.8-x in git?That way bigger changes can still go
>>>>>
>>>>>> into the 4.x branches, while bugs are fixed in 4.8-x branches.
>>>>>> -- Lars
>>>>>>
>>>>>> From: James Taylor<ja...@apache.org>
>>>>>> To: "dev@phoenix.apache.org"<de...@phoenix.apache.org>
>>>>>> Sent: Thursday, July 21, 2016 7:16 PM
>>>>>> Subject: new 4.8.0 RC?
>>>>>>
>>>>>> How about a cutting a new RC now that the licensing work is complete,
>>>>>> Ankit? Looks like we can simplify the voting too by just having a
>>>>>> single
>>>>>> vote across all versions by just include all the information in one
>>>>>> VOTE
>>>>>> thread.
>>>>>>
>>>>>> Would be good to get PHOENIX-3078 in too, if possible. We've had a few
>>>>>> other fixes come in which IMHO are all ok to include in the new RC.
>>>>>>
>>>>>> Thanks,
>>>>>> James
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>
Re: new 4.8.0 RC?
Posted by Josh Elser <jo...@gmail.com>.
Either works for me. The two changes I'm committing today have just gone
to 8 branches instead of 4.
Ankit, do you have a preference as RM what to do?
James Taylor wrote:
> We should, but I don't think anything has been committed against the 4.x
> branches that doesn't belong in the release. Maybe we should just delete
> the 4.8 branches and recreate them once the RC is up?
>
> On Tue, Aug 2, 2016 at 8:28 AM, Josh Elser<jo...@gmail.com> wrote:
>
>> Shouldn't we bump the 4.x and master branch to 4.9.0-HBase**-SNAPSHOT? I
>> just noticed that we have the same Maven versions on both the 4.8 and 4.x
>> branch sets.
>>
>>
>> Ankit Singhal wrote:
>>
>>> Following 4 branches have been created and are now available for commits
>>> targeted for 4.8.0 only.
>>>
>>> 4.8-HBase-0.98 (from 4.x-HBase-0.98)
>>> 4.8-HBase-1.0 (from 4.x-HBase-1.0)
>>> 4.8-HBase-1.1 (from 4.x-HBase-1.1)
>>> 4.8-HBase-1.2 (from master)
>>>
>>> Any commit targeted for 4.8.1 or 4.9+ along with 4.8.0 can go in master
>>> and
>>> 4.x branches now.
>>>
>>> Regards,
>>> Ankit Singhal
>>>
>>> On Thu, Jul 28, 2016 at 4:25 PM, Ankit Singhal<an...@gmail.com>
>>> wrote:
>>>
>>> Ok, Given that 4.8.0 RC is taking time , we can fork 4.8-HBase-x.y
>>>> branches so that new features and bugs target for future releases(4.9+)
>>>> can
>>>> be committed in 4.x branches and master.
>>>>
>>>> Whatever is targeted for 4.8.0 needs to be committed in all 8
>>>> branches(three 4.x branches , master, four 4.8-HBase-x.y) as all 4.8
>>>> releases(including 4.8.0 or 4.8.x) will be done from 4.8-HBase-x.y
>>>> branches.
>>>>
>>>> I'll create the following new branches tomorrow morning IST,
>>>> 4.8-HBase-0.98 (from 4.x-HBase-0.98)
>>>> 4.8-HBase-1.0 (from 4.x-HBase-1.0)
>>>> 4.8-HBase-1.1 (from 4.x-HBase-1.1)
>>>> 4.8-HBase-1.2 (from master)
>>>>
>>>> Let's discuss if someone has any concerns.
>>>>
>>>> Regards,
>>>> Ankit Singhal
>>>>
>>>> On Sun, Jul 24, 2016 at 2:19 PM,<la...@apache.org> wrote:
>>>>
>>>> Also, can we branch 4.8-x in git?That way bigger changes can still go
>>>>> into the 4.x branches, while bugs are fixed in 4.8-x branches.
>>>>> -- Lars
>>>>>
>>>>> From: James Taylor<ja...@apache.org>
>>>>> To: "dev@phoenix.apache.org"<de...@phoenix.apache.org>
>>>>> Sent: Thursday, July 21, 2016 7:16 PM
>>>>> Subject: new 4.8.0 RC?
>>>>>
>>>>> How about a cutting a new RC now that the licensing work is complete,
>>>>> Ankit? Looks like we can simplify the voting too by just having a single
>>>>> vote across all versions by just include all the information in one VOTE
>>>>> thread.
>>>>>
>>>>> Would be good to get PHOENIX-3078 in too, if possible. We've had a few
>>>>> other fixes come in which IMHO are all ok to include in the new RC.
>>>>>
>>>>> Thanks,
>>>>> James
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>
Re: new 4.8.0 RC?
Posted by James Taylor <ja...@apache.org>.
We should, but I don't think anything has been committed against the 4.x
branches that doesn't belong in the release. Maybe we should just delete
the 4.8 branches and recreate them once the RC is up?
On Tue, Aug 2, 2016 at 8:28 AM, Josh Elser <jo...@gmail.com> wrote:
> Shouldn't we bump the 4.x and master branch to 4.9.0-HBase**-SNAPSHOT? I
> just noticed that we have the same Maven versions on both the 4.8 and 4.x
> branch sets.
>
>
> Ankit Singhal wrote:
>
>> Following 4 branches have been created and are now available for commits
>> targeted for 4.8.0 only.
>>
>> 4.8-HBase-0.98 (from 4.x-HBase-0.98)
>> 4.8-HBase-1.0 (from 4.x-HBase-1.0)
>> 4.8-HBase-1.1 (from 4.x-HBase-1.1)
>> 4.8-HBase-1.2 (from master)
>>
>> Any commit targeted for 4.8.1 or 4.9+ along with 4.8.0 can go in master
>> and
>> 4.x branches now.
>>
>> Regards,
>> Ankit Singhal
>>
>> On Thu, Jul 28, 2016 at 4:25 PM, Ankit Singhal<an...@gmail.com>
>> wrote:
>>
>> Ok, Given that 4.8.0 RC is taking time , we can fork 4.8-HBase-x.y
>>> branches so that new features and bugs target for future releases(4.9+)
>>> can
>>> be committed in 4.x branches and master.
>>>
>>> Whatever is targeted for 4.8.0 needs to be committed in all 8
>>> branches(three 4.x branches , master, four 4.8-HBase-x.y) as all 4.8
>>> releases(including 4.8.0 or 4.8.x) will be done from 4.8-HBase-x.y
>>> branches.
>>>
>>> I'll create the following new branches tomorrow morning IST,
>>> 4.8-HBase-0.98 (from 4.x-HBase-0.98)
>>> 4.8-HBase-1.0 (from 4.x-HBase-1.0)
>>> 4.8-HBase-1.1 (from 4.x-HBase-1.1)
>>> 4.8-HBase-1.2 (from master)
>>>
>>> Let's discuss if someone has any concerns.
>>>
>>> Regards,
>>> Ankit Singhal
>>>
>>> On Sun, Jul 24, 2016 at 2:19 PM,<la...@apache.org> wrote:
>>>
>>> Also, can we branch 4.8-x in git?That way bigger changes can still go
>>>> into the 4.x branches, while bugs are fixed in 4.8-x branches.
>>>> -- Lars
>>>>
>>>> From: James Taylor<ja...@apache.org>
>>>> To: "dev@phoenix.apache.org"<de...@phoenix.apache.org>
>>>> Sent: Thursday, July 21, 2016 7:16 PM
>>>> Subject: new 4.8.0 RC?
>>>>
>>>> How about a cutting a new RC now that the licensing work is complete,
>>>> Ankit? Looks like we can simplify the voting too by just having a single
>>>> vote across all versions by just include all the information in one VOTE
>>>> thread.
>>>>
>>>> Would be good to get PHOENIX-3078 in too, if possible. We've had a few
>>>> other fixes come in which IMHO are all ok to include in the new RC.
>>>>
>>>> Thanks,
>>>> James
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>