Re: [DISCUSS] 2.7.3 release?

2016-03-29 Thread Vinod Kumar Vavilapalli
Sorry, I got busy offline on various things for a couple of months - so 2.7.3 
suffered.

2.8.0 also suffered, but because javadocs etc are completely broken on 
branch-2, and I had spent quite a bit of time narrowing down all the backports 
needed, sigh.

Will spend some time this week and the next.

+Vinod

> On Mar 29, 2016, at 9:18 AM, Sean Busbey  wrote:
> 
> It's been about 2 months since 2.7.2 came out, and there are currently
> 135 issues in resolved status with a fixVersion of 2.7.3:
> 
>  * 32 Common
>  * 52 HDFS
>  * 33 YARN
>  * 18 MAPREDUCE
> 
> Could we move towards a release soon?
> 
> -- 
> busbey
> 



Re: [DISCUSS] 2.7.3 release?

2016-03-29 Thread Sean Busbey
Could we train up some additional volunteers to act as release
managers? We shouldn't put all the weight of running maintenance
releases on just you Vinod.

On Tue, Mar 29, 2016 at 12:33 PM, Vinod Kumar Vavilapalli
 wrote:
> Sorry, I got busy offline on various things for a couple of months - so 2.7.3 
> suffered.
>
> 2.8.0 also suffered, but because javadocs etc are completely broken on 
> branch-2, and I had spent quite a bit of time narrowing down all the 
> backports needed, sigh.
>
> Will spend some time this week and the next.
>
> +Vinod
>
>> On Mar 29, 2016, at 9:18 AM, Sean Busbey  wrote:
>>
>> It's been about 2 months since 2.7.2 came out, and there are currently
>> 135 issues in resolved status with a fixVersion of 2.7.3:
>>
>>  * 32 Common
>>  * 52 HDFS
>>  * 33 YARN
>>  * 18 MAPREDUCE
>>
>> Could we move towards a release soon?
>>
>> --
>> busbey
>>
>



-- 
busbey


Re: [DISCUSS] 2.7.3 release?

2016-03-29 Thread Akira AJISAKA

I'd like to help the release process as a release manager.
First, I'll look into the jiras in the following lists.

* 2.7.3 critical/blocker issues (19): https://s.apache.org/X5pt
* 2.8.0 critical/blocker issues (61): https://s.apache.org/SXuo

We should fix them as soon as possible to release 2.7.3/2.8.0 earlier.

Regards,
Akira

On 3/30/16 02:56, Sean Busbey wrote:

Could we train up some additional volunteers to act as release
managers? We shouldn't put all the weight of running maintenance
releases on just you Vinod.

On Tue, Mar 29, 2016 at 12:33 PM, Vinod Kumar Vavilapalli
 wrote:

Sorry, I got busy offline on various things for a couple of months - so 2.7.3 
suffered.

2.8.0 also suffered, but because javadocs etc are completely broken on 
branch-2, and I had spent quite a bit of time narrowing down all the backports 
needed, sigh.

Will spend some time this week and the next.

+Vinod


On Mar 29, 2016, at 9:18 AM, Sean Busbey  wrote:

It's been about 2 months since 2.7.2 came out, and there are currently
135 issues in resolved status with a fixVersion of 2.7.3:

  * 32 Common
  * 52 HDFS
  * 33 YARN
  * 18 MAPREDUCE

Could we move towards a release soon?

--
busbey











Re: [DISCUSS] 2.7.3 release?

2016-03-30 Thread Steve Loughran

> On 30 Mar 2016, at 07:42, Akira AJISAKA  wrote:
> 
> I'd like to help the release process as a release manager.
> First, I'll look into the jiras in the following lists.
> 
> * 2.7.3 critical/blocker issues (19): https://s.apache.org/X5pt
> * 2.8.0 critical/blocker issues (61): https://s.apache.org/SXuo
> 
> We should fix them as soon as possible to release 2.7.3/2.8.0 earlier.
> 
> Regards,
> Akira

Looking at some more possible backports, I'm wondering at

HADOOP-12577 -> 2.6.x : commons collection update for security
HADOOP-11628 -> 2.7  : that's SPNEGO+CNAMES in JDK8