You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by Vinod Kumar Vavilapalli <vi...@apache.org> on 2016/06/14 22:54:17 UTC
Re: 2.7.3 release plan
HADOOP-12893 is finally close to completion after > 3months thanks to efforts from Akira AJISAKA, Xiao Chen and Andrew Wang.
I’m creating the release branch and kickstarting the release activities.
Thanks
+Vinod
> On May 16, 2016, at 5:39 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> I am just waiting on HADOOP-12893.
>
> HADOOP-13154 just got created in the last one day, will have to see if it really should block the release.
>
> Major tickets are usually taken on a time basis: if they get in by the proposed timelines, we get them in. Otherwise, we move them over.
>
> Thanks
> +Vinod
>
>> On May 16, 2016, at 5:20 PM, larry mccay <lm...@apache.org> wrote:
>>
>> Curious on the status of 2.7.3....
>>
>> It seems that we still have two outstanding critical/blocker JIRAs:
>>
>> 1. [image: Bug] HADOOP-12893
>> Verify LICENSE.txt and NOTICE.txt
>> <https://issues.apache.org/jira/browse/HADOOP-12893>
>> 2. [image: Sub-task] HADOOP-13154
>> <https://issues.apache.org/jira/browse/HADOOP-13154>S3AFileSystem
>> printAmazonServiceException/printAmazonClientException appear copy & paste
>> of AWS examples <https://issues.apache.org/jira/browse/HADOOP-13154>
>>
>>
>> But 45-ish when we include Majors as well.
>>
>> I know there are a number of critical issues with fixes that need to go out.
>>
>> What is the plan?
>>
>> On Tue, Apr 12, 2016 at 2:09 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
>>> wrote:
>>
>>> Others and I committed a few, I pushed out a few.
>>>
>>> Down to just three now!
>>>
>>> +Vinod
>>>
>>>> On Apr 6, 2016, at 3:00 PM, Vinod Kumar Vavilapalli <vi...@apache.org>
>>> wrote:
>>>>
>>>> Down to only 10 blocker / critical tickets (
>>> https://issues.apache.org/jira/issues/?filter=12335343 <
>>> https://issues.apache.org/jira/issues/?filter=12335343>) now!
>>>>
>>>> Thanks
>>>> +Vinod
>>>>
>>>>> On Mar 30, 2016, at 4:18 PM, Vinod Kumar Vavilapalli <
>>> vinodkv@apache.org <ma...@apache.org>> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> Got nudged about 2.7.3. Was previously waiting for 2.6.4 to go out
>>> (which did go out mid February). Got a little busy since.
>>>>>
>>>>> Following up the 2.7.2 maintenance release, we should work towards a
>>> 2.7.3. The focus obviously is to have blocker issues [1], bug-fixes and
>>> *no* features / improvements.
>>>>>
>>>>> I hope to cut an RC in a week - giving enough time for outstanding
>>> blocker / critical issues. Will start moving out any tickets that are not
>>> blockers and/or won’t fit the timeline - there are 3 blockers and 15
>>> critical tickets outstanding as of now.
>>>>>
>>>>> Thanks,
>>>>> +Vinod
>>>>>
>>>>> [1] 2.7.3 release blockers:
>>> https://issues.apache.org/jira/issues/?filter=12335343 <
>>> https://issues.apache.org/jira/issues/?filter=12335343>
>>>>
>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: 2.7.3 release plan
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
The nexus issue persists to date. I have been constantly getting “Remote end closed due to a SSH handshake” issue. Tried to upload the artifacts in piece, but that was too slow, spanned across days.
Finally found a “ DretryFailedDeploymentCount=10” option to mvn-deploy.
Sending out the vote now.
Thanks
+Vinod
> On Jul 21, 2016, at 11:53 AM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> Started on the RC two days ago, but running into a nexus issue - not able to push the jars up stream for two days - the remote end is dropping the connection consistently.
>
> Trying to figure out workarounds.
>
> Thanks
> +Vinod
>
>> On Jul 13, 2016, at 4:09 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>>
>> HADOOP-12893 is done after 4 months, thanks to great work from a bunch of folks besides Xiao Chen.
>>
>> Creating the RC now.
>>
>> Thanks
>> +Vinod
>>
>>> On Jun 14, 2016, at 7:28 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>>>
>>> Release branch 2.7.3 is created. I also updated branch-2.7 to point to 2.7.4-SNAPSHOT now.
>>>
>>> Thanks
>>> +Vinod
>>>
>>>> On Jun 14, 2016, at 3:54 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>>>>
>>>> HADOOP-12893 is finally close to completion after > 3months thanks to efforts from Akira AJISAKA, Xiao Chen and Andrew Wang.
>>>>
>>>> I’m creating the release branch and kickstarting the release activities.
>>>>
>>>> Thanks
>>>> +Vinod
>>>>
>>>>> On May 16, 2016, at 5:39 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>>>>>
>>>>> I am just waiting on HADOOP-12893.
>>>>>
>>>>> HADOOP-13154 just got created in the last one day, will have to see if it really should block the release.
>>>>>
>>>>> Major tickets are usually taken on a time basis: if they get in by the proposed timelines, we get them in. Otherwise, we move them over.
>>>>>
>>>>> Thanks
>>>>> +Vinod
>>>>>
>>>>>> On May 16, 2016, at 5:20 PM, larry mccay <lm...@apache.org> wrote:
>>>>>>
>>>>>> Curious on the status of 2.7.3....
>>>>>>
>>>>>> It seems that we still have two outstanding critical/blocker JIRAs:
>>>>>>
>>>>>> 1. [image: Bug] HADOOP-12893
>>>>>> Verify LICENSE.txt and NOTICE.txt
>>>>>> <https://issues.apache.org/jira/browse/HADOOP-12893>
>>>>>> 2. [image: Sub-task] HADOOP-13154
>>>>>> <https://issues.apache.org/jira/browse/HADOOP-13154>S3AFileSystem
>>>>>> printAmazonServiceException/printAmazonClientException appear copy & paste
>>>>>> of AWS examples <https://issues.apache.org/jira/browse/HADOOP-13154>
>>>>>>
>>>>>>
>>>>>> But 45-ish when we include Majors as well.
>>>>>>
>>>>>> I know there are a number of critical issues with fixes that need to go out.
>>>>>>
>>>>>> What is the plan?
>>>>>>
>>>>>> On Tue, Apr 12, 2016 at 2:09 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
>>>>>>> wrote:
>>>>>>
>>>>>>> Others and I committed a few, I pushed out a few.
>>>>>>>
>>>>>>> Down to just three now!
>>>>>>>
>>>>>>> +Vinod
>>>>>>>
>>>>>>>> On Apr 6, 2016, at 3:00 PM, Vinod Kumar Vavilapalli <vi...@apache.org>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Down to only 10 blocker / critical tickets (
>>>>>>> https://issues.apache.org/jira/issues/?filter=12335343 <
>>>>>>> https://issues.apache.org/jira/issues/?filter=12335343>) now!
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> +Vinod
>>>>>>>>
>>>>>>>>> On Mar 30, 2016, at 4:18 PM, Vinod Kumar Vavilapalli <
>>>>>>> vinodkv@apache.org <ma...@apache.org>> wrote:
>>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> Got nudged about 2.7.3. Was previously waiting for 2.6.4 to go out
>>>>>>> (which did go out mid February). Got a little busy since.
>>>>>>>>>
>>>>>>>>> Following up the 2.7.2 maintenance release, we should work towards a
>>>>>>> 2.7.3. The focus obviously is to have blocker issues [1], bug-fixes and
>>>>>>> *no* features / improvements.
>>>>>>>>>
>>>>>>>>> I hope to cut an RC in a week - giving enough time for outstanding
>>>>>>> blocker / critical issues. Will start moving out any tickets that are not
>>>>>>> blockers and/or won’t fit the timeline - there are 3 blockers and 15
>>>>>>> critical tickets outstanding as of now.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> +Vinod
>>>>>>>>>
>>>>>>>>> [1] 2.7.3 release blockers:
>>>>>>> https://issues.apache.org/jira/issues/?filter=12335343 <
>>>>>>> https://issues.apache.org/jira/issues/?filter=12335343>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: 2.7.3 release plan
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Started on the RC two days ago, but running into a nexus issue - not able to push the jars up stream for two days - the remote end is dropping the connection consistently.
Trying to figure out workarounds.
Thanks
+Vinod
> On Jul 13, 2016, at 4:09 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> HADOOP-12893 is done after 4 months, thanks to great work from a bunch of folks besides Xiao Chen.
>
> Creating the RC now.
>
> Thanks
> +Vinod
>
>> On Jun 14, 2016, at 7:28 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>>
>> Release branch 2.7.3 is created. I also updated branch-2.7 to point to 2.7.4-SNAPSHOT now.
>>
>> Thanks
>> +Vinod
>>
>>> On Jun 14, 2016, at 3:54 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>>>
>>> HADOOP-12893 is finally close to completion after > 3months thanks to efforts from Akira AJISAKA, Xiao Chen and Andrew Wang.
>>>
>>> I’m creating the release branch and kickstarting the release activities.
>>>
>>> Thanks
>>> +Vinod
>>>
>>>> On May 16, 2016, at 5:39 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>>>>
>>>> I am just waiting on HADOOP-12893.
>>>>
>>>> HADOOP-13154 just got created in the last one day, will have to see if it really should block the release.
>>>>
>>>> Major tickets are usually taken on a time basis: if they get in by the proposed timelines, we get them in. Otherwise, we move them over.
>>>>
>>>> Thanks
>>>> +Vinod
>>>>
>>>>> On May 16, 2016, at 5:20 PM, larry mccay <lm...@apache.org> wrote:
>>>>>
>>>>> Curious on the status of 2.7.3....
>>>>>
>>>>> It seems that we still have two outstanding critical/blocker JIRAs:
>>>>>
>>>>> 1. [image: Bug] HADOOP-12893
>>>>> Verify LICENSE.txt and NOTICE.txt
>>>>> <https://issues.apache.org/jira/browse/HADOOP-12893>
>>>>> 2. [image: Sub-task] HADOOP-13154
>>>>> <https://issues.apache.org/jira/browse/HADOOP-13154>S3AFileSystem
>>>>> printAmazonServiceException/printAmazonClientException appear copy & paste
>>>>> of AWS examples <https://issues.apache.org/jira/browse/HADOOP-13154>
>>>>>
>>>>>
>>>>> But 45-ish when we include Majors as well.
>>>>>
>>>>> I know there are a number of critical issues with fixes that need to go out.
>>>>>
>>>>> What is the plan?
>>>>>
>>>>> On Tue, Apr 12, 2016 at 2:09 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
>>>>>> wrote:
>>>>>
>>>>>> Others and I committed a few, I pushed out a few.
>>>>>>
>>>>>> Down to just three now!
>>>>>>
>>>>>> +Vinod
>>>>>>
>>>>>>> On Apr 6, 2016, at 3:00 PM, Vinod Kumar Vavilapalli <vi...@apache.org>
>>>>>> wrote:
>>>>>>>
>>>>>>> Down to only 10 blocker / critical tickets (
>>>>>> https://issues.apache.org/jira/issues/?filter=12335343 <
>>>>>> https://issues.apache.org/jira/issues/?filter=12335343>) now!
>>>>>>>
>>>>>>> Thanks
>>>>>>> +Vinod
>>>>>>>
>>>>>>>> On Mar 30, 2016, at 4:18 PM, Vinod Kumar Vavilapalli <
>>>>>> vinodkv@apache.org <ma...@apache.org>> wrote:
>>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> Got nudged about 2.7.3. Was previously waiting for 2.6.4 to go out
>>>>>> (which did go out mid February). Got a little busy since.
>>>>>>>>
>>>>>>>> Following up the 2.7.2 maintenance release, we should work towards a
>>>>>> 2.7.3. The focus obviously is to have blocker issues [1], bug-fixes and
>>>>>> *no* features / improvements.
>>>>>>>>
>>>>>>>> I hope to cut an RC in a week - giving enough time for outstanding
>>>>>> blocker / critical issues. Will start moving out any tickets that are not
>>>>>> blockers and/or won’t fit the timeline - there are 3 blockers and 15
>>>>>> critical tickets outstanding as of now.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> +Vinod
>>>>>>>>
>>>>>>>> [1] 2.7.3 release blockers:
>>>>>> https://issues.apache.org/jira/issues/?filter=12335343 <
>>>>>> https://issues.apache.org/jira/issues/?filter=12335343>
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>>
>>>>
>>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: 2.7.3 release plan
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
HADOOP-12893 is done after 4 months, thanks to great work from a bunch of folks besides Xiao Chen.
Creating the RC now.
Thanks
+Vinod
> On Jun 14, 2016, at 7:28 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> Release branch 2.7.3 is created. I also updated branch-2.7 to point to 2.7.4-SNAPSHOT now.
>
> Thanks
> +Vinod
>
>> On Jun 14, 2016, at 3:54 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>>
>> HADOOP-12893 is finally close to completion after > 3months thanks to efforts from Akira AJISAKA, Xiao Chen and Andrew Wang.
>>
>> I’m creating the release branch and kickstarting the release activities.
>>
>> Thanks
>> +Vinod
>>
>>> On May 16, 2016, at 5:39 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>>>
>>> I am just waiting on HADOOP-12893.
>>>
>>> HADOOP-13154 just got created in the last one day, will have to see if it really should block the release.
>>>
>>> Major tickets are usually taken on a time basis: if they get in by the proposed timelines, we get them in. Otherwise, we move them over.
>>>
>>> Thanks
>>> +Vinod
>>>
>>>> On May 16, 2016, at 5:20 PM, larry mccay <lm...@apache.org> wrote:
>>>>
>>>> Curious on the status of 2.7.3....
>>>>
>>>> It seems that we still have two outstanding critical/blocker JIRAs:
>>>>
>>>> 1. [image: Bug] HADOOP-12893
>>>> Verify LICENSE.txt and NOTICE.txt
>>>> <https://issues.apache.org/jira/browse/HADOOP-12893>
>>>> 2. [image: Sub-task] HADOOP-13154
>>>> <https://issues.apache.org/jira/browse/HADOOP-13154>S3AFileSystem
>>>> printAmazonServiceException/printAmazonClientException appear copy & paste
>>>> of AWS examples <https://issues.apache.org/jira/browse/HADOOP-13154>
>>>>
>>>>
>>>> But 45-ish when we include Majors as well.
>>>>
>>>> I know there are a number of critical issues with fixes that need to go out.
>>>>
>>>> What is the plan?
>>>>
>>>> On Tue, Apr 12, 2016 at 2:09 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
>>>>> wrote:
>>>>
>>>>> Others and I committed a few, I pushed out a few.
>>>>>
>>>>> Down to just three now!
>>>>>
>>>>> +Vinod
>>>>>
>>>>>> On Apr 6, 2016, at 3:00 PM, Vinod Kumar Vavilapalli <vi...@apache.org>
>>>>> wrote:
>>>>>>
>>>>>> Down to only 10 blocker / critical tickets (
>>>>> https://issues.apache.org/jira/issues/?filter=12335343 <
>>>>> https://issues.apache.org/jira/issues/?filter=12335343>) now!
>>>>>>
>>>>>> Thanks
>>>>>> +Vinod
>>>>>>
>>>>>>> On Mar 30, 2016, at 4:18 PM, Vinod Kumar Vavilapalli <
>>>>> vinodkv@apache.org <ma...@apache.org>> wrote:
>>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Got nudged about 2.7.3. Was previously waiting for 2.6.4 to go out
>>>>> (which did go out mid February). Got a little busy since.
>>>>>>>
>>>>>>> Following up the 2.7.2 maintenance release, we should work towards a
>>>>> 2.7.3. The focus obviously is to have blocker issues [1], bug-fixes and
>>>>> *no* features / improvements.
>>>>>>>
>>>>>>> I hope to cut an RC in a week - giving enough time for outstanding
>>>>> blocker / critical issues. Will start moving out any tickets that are not
>>>>> blockers and/or won’t fit the timeline - there are 3 blockers and 15
>>>>> critical tickets outstanding as of now.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> +Vinod
>>>>>>>
>>>>>>> [1] 2.7.3 release blockers:
>>>>> https://issues.apache.org/jira/issues/?filter=12335343 <
>>>>> https://issues.apache.org/jira/issues/?filter=12335343>
>>>>>>
>>>>>
>>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: 2.7.3 release plan
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
Release branch 2.7.3 is created. I also updated branch-2.7 to point to 2.7.4-SNAPSHOT now.
Thanks
+Vinod
> On Jun 14, 2016, at 3:54 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>
> HADOOP-12893 is finally close to completion after > 3months thanks to efforts from Akira AJISAKA, Xiao Chen and Andrew Wang.
>
> I’m creating the release branch and kickstarting the release activities.
>
> Thanks
> +Vinod
>
>> On May 16, 2016, at 5:39 PM, Vinod Kumar Vavilapalli <vi...@apache.org> wrote:
>>
>> I am just waiting on HADOOP-12893.
>>
>> HADOOP-13154 just got created in the last one day, will have to see if it really should block the release.
>>
>> Major tickets are usually taken on a time basis: if they get in by the proposed timelines, we get them in. Otherwise, we move them over.
>>
>> Thanks
>> +Vinod
>>
>>> On May 16, 2016, at 5:20 PM, larry mccay <lm...@apache.org> wrote:
>>>
>>> Curious on the status of 2.7.3....
>>>
>>> It seems that we still have two outstanding critical/blocker JIRAs:
>>>
>>> 1. [image: Bug] HADOOP-12893
>>> Verify LICENSE.txt and NOTICE.txt
>>> <https://issues.apache.org/jira/browse/HADOOP-12893>
>>> 2. [image: Sub-task] HADOOP-13154
>>> <https://issues.apache.org/jira/browse/HADOOP-13154>S3AFileSystem
>>> printAmazonServiceException/printAmazonClientException appear copy & paste
>>> of AWS examples <https://issues.apache.org/jira/browse/HADOOP-13154>
>>>
>>>
>>> But 45-ish when we include Majors as well.
>>>
>>> I know there are a number of critical issues with fixes that need to go out.
>>>
>>> What is the plan?
>>>
>>> On Tue, Apr 12, 2016 at 2:09 PM, Vinod Kumar Vavilapalli <vinodkv@apache.org
>>>> wrote:
>>>
>>>> Others and I committed a few, I pushed out a few.
>>>>
>>>> Down to just three now!
>>>>
>>>> +Vinod
>>>>
>>>>> On Apr 6, 2016, at 3:00 PM, Vinod Kumar Vavilapalli <vi...@apache.org>
>>>> wrote:
>>>>>
>>>>> Down to only 10 blocker / critical tickets (
>>>> https://issues.apache.org/jira/issues/?filter=12335343 <
>>>> https://issues.apache.org/jira/issues/?filter=12335343>) now!
>>>>>
>>>>> Thanks
>>>>> +Vinod
>>>>>
>>>>>> On Mar 30, 2016, at 4:18 PM, Vinod Kumar Vavilapalli <
>>>> vinodkv@apache.org <ma...@apache.org>> wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Got nudged about 2.7.3. Was previously waiting for 2.6.4 to go out
>>>> (which did go out mid February). Got a little busy since.
>>>>>>
>>>>>> Following up the 2.7.2 maintenance release, we should work towards a
>>>> 2.7.3. The focus obviously is to have blocker issues [1], bug-fixes and
>>>> *no* features / improvements.
>>>>>>
>>>>>> I hope to cut an RC in a week - giving enough time for outstanding
>>>> blocker / critical issues. Will start moving out any tickets that are not
>>>> blockers and/or won’t fit the timeline - there are 3 blockers and 15
>>>> critical tickets outstanding as of now.
>>>>>>
>>>>>> Thanks,
>>>>>> +Vinod
>>>>>>
>>>>>> [1] 2.7.3 release blockers:
>>>> https://issues.apache.org/jira/issues/?filter=12335343 <
>>>> https://issues.apache.org/jira/issues/?filter=12335343>
>>>>>
>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org