You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tez.apache.org by Andre Kelpe <ak...@concurrentinc.com> on 2015/05/01 00:20:22 UTC
Re: 0.7.0 release
Hi,
Can you give an update on the 0.6.1 progress before you release 0.7? How
will those branches compare? Will you port the fixes fro 0.6.1 over to 0.7?
- André
On Thu, Apr 30, 2015 at 11:57 PM, Hitesh Shah <hi...@apache.org> wrote:
> Hi folks,
>
> Based on some offline discussions with some folks from Pig, it looks like
> they have branched out in anticipation for their 0.15 release and they are
> looking for a 0.7.0 release. With that in mind, we should start looking at
> doing the same so as to unblock them.
>
> Any volunteers to drive the 0.7.0 release?
>
> thanks
> — Hitesh
--
André Kelpe
andre@concurrentinc.com
http://concurrentinc.com
Re: 0.7.0 release
Posted by Jonathan Eagles <je...@gmail.com>.
Well said, Hitesh. There are just a few remaining issues targeted to
0.6.1 that need to be considered before creating a release candidate.
You can expect an rc candidate soon on this.
Jon
On Thu, Apr 30, 2015 at 5:31 PM, Hitesh Shah <hi...@apache.org> wrote:
> Hello Andre,
>
> Over the past couple of weeks, we have been driving some of the blockers for 0.6.1 to a close. I think Jon Eagles who drove the 0.6.0 release is probably going to be looking at doing a 0.6.1 release very shortly too.
>
> Looking at [1], the 0.5.4 release is pretty much ready to go.
> There are a few issues to be sorted for 0.6.1 [2] and 0.7.0 has a bunch more [3].
>
> For the most part, anything released in 0.6.1 should also be in 0.7.0 ( unless for some unforseen reason, the 0.6.1 release goes after 0.7.0 ). The usual commit process is commit to master and then back port to the necessary older maintenance branches ( so anything on branch-0.6 should also already be on master which is where branch 0.7 will be cut from ).
>
> thanks
> — Hitesh
>
> [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20%22Target%20Version%2Fs%22%20%3D%200.5.4%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> [2] https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20%22Target%20Version%2Fs%22%20%3D%200.6.1%20AND%20resolution%20%3D%20Unresolved%20and%20priority%20in%20(Blocker%2C%20Critical)%20ORDER%20BY%20priority%20DESC
> [3] https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20%22Target%20Version%2Fs%22%20%3D%200.7.0%20AND%20resolution%20%3D%20Unresolved%20and%20priority%20in%20(Blocker%2C%20Critical)%20ORDER%20BY%20priority%20DESC
>
>
> On Apr 30, 2015, at 3:20 PM, Andre Kelpe <ak...@concurrentinc.com> wrote:
>
>> Hi,
>>
>> Can you give an update on the 0.6.1 progress before you release 0.7? How
>> will those branches compare? Will you port the fixes fro 0.6.1 over to 0.7?
>>
>> - André
>>
>> On Thu, Apr 30, 2015 at 11:57 PM, Hitesh Shah <hi...@apache.org> wrote:
>>
>>> Hi folks,
>>>
>>> Based on some offline discussions with some folks from Pig, it looks like
>>> they have branched out in anticipation for their 0.15 release and they are
>>> looking for a 0.7.0 release. With that in mind, we should start looking at
>>> doing the same so as to unblock them.
>>>
>>> Any volunteers to drive the 0.7.0 release?
>>>
>>> thanks
>>> — Hitesh
>>
>>
>>
>>
>> --
>> André Kelpe
>> andre@concurrentinc.com
>> http://concurrentinc.com
>
Re: 0.7.0 release
Posted by Hitesh Shah <hi...@apache.org>.
Hello Andre,
Over the past couple of weeks, we have been driving some of the blockers for 0.6.1 to a close. I think Jon Eagles who drove the 0.6.0 release is probably going to be looking at doing a 0.6.1 release very shortly too.
Looking at [1], the 0.5.4 release is pretty much ready to go.
There are a few issues to be sorted for 0.6.1 [2] and 0.7.0 has a bunch more [3].
For the most part, anything released in 0.6.1 should also be in 0.7.0 ( unless for some unforseen reason, the 0.6.1 release goes after 0.7.0 ). The usual commit process is commit to master and then back port to the necessary older maintenance branches ( so anything on branch-0.6 should also already be on master which is where branch 0.7 will be cut from ).
thanks
— Hitesh
[1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20%22Target%20Version%2Fs%22%20%3D%200.5.4%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
[2] https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20%22Target%20Version%2Fs%22%20%3D%200.6.1%20AND%20resolution%20%3D%20Unresolved%20and%20priority%20in%20(Blocker%2C%20Critical)%20ORDER%20BY%20priority%20DESC
[3] https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20%22Target%20Version%2Fs%22%20%3D%200.7.0%20AND%20resolution%20%3D%20Unresolved%20and%20priority%20in%20(Blocker%2C%20Critical)%20ORDER%20BY%20priority%20DESC
On Apr 30, 2015, at 3:20 PM, Andre Kelpe <ak...@concurrentinc.com> wrote:
> Hi,
>
> Can you give an update on the 0.6.1 progress before you release 0.7? How
> will those branches compare? Will you port the fixes fro 0.6.1 over to 0.7?
>
> - André
>
> On Thu, Apr 30, 2015 at 11:57 PM, Hitesh Shah <hi...@apache.org> wrote:
>
>> Hi folks,
>>
>> Based on some offline discussions with some folks from Pig, it looks like
>> they have branched out in anticipation for their 0.15 release and they are
>> looking for a 0.7.0 release. With that in mind, we should start looking at
>> doing the same so as to unblock them.
>>
>> Any volunteers to drive the 0.7.0 release?
>>
>> thanks
>> — Hitesh
>
>
>
>
> --
> André Kelpe
> andre@concurrentinc.com
> http://concurrentinc.com