The vote passed with 15 +1's (9 binding) and 0 -1's. I will start the
release today.
Thanks,
Tom
On 5/17/13 4:10 PM, "Thomas Graves" wrote:
>Hello all,
>
>We've had a few critical issues come up in 0.23.7 that I think warrants a
>0.23.8 release. The main one is MAPREDUCE-5211. There are a cou
+1
On 05/17/2013 04:10 PM, Thomas Graves wrote:
Hello all,
We've had a few critical issues come up in 0.23.7 that I think warrants a
0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of
other issues that I want finished up and get in before we spin it. Those
include HDFS-3875
+1
On 5/17/13 4:10 PM, "Thomas Graves" wrote:
>Hello all,
>
>We've had a few critical issues come up in 0.23.7 that I think warrants a
>0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of
>other issues that I want finished up and get in before we spin it. Those
>include HDFS-
+1.
On Fri, May 17, 2013 at 2:10 PM, Thomas Graves wrote:
> Hello all,
>
> We've had a few critical issues come up in 0.23.7 that I think warrants a
> 0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of
> other issues that I want finished up and get in before we spin it. Thos
+1
--
Arpit Gupta
Hortonworks Inc.
http://hortonworks.com/
On May 17, 2013, at 2:10 PM, Thomas Graves wrote:
> Hello all,
>
> We've had a few critical issues come up in 0.23.7 that I think warrants a
> 0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of
> other issues that I
Thanks Chris, I'll take a look at HDFS-3180.
Tom
On 5/19/13 12:54 PM, "Chris Nauroth" wrote:
>+1 (non-binding)
>
>BTW, I left a comment on HDFS-4835 suggesting that you include HDFS-3180
>for WebHDFS socket connect/read timeouts. It's up to you. (I'm voting +1
>for the release plan either way
+1 (non-binding)
On Sun, May 19, 2013 at 6:23 PM, Sandy Ryza wrote:
> +1 (non-binding)
>
>
> On Sun, May 19, 2013 at 1:22 PM, Derek Dagit wrote:
>
> > +1 (non-binding)
> >
> > On May 17, 2013, at 4:14 PM, "Thomas Graves"
> > wrote:
> >
> > > Hello all,
> > >
> > > We've had a few critical iss
+1 (non-binding)
On May 17, 2013, at 4:14 PM, "Thomas Graves" wrote:
> Hello all,
>
> We've had a few critical issues come up in 0.23.7 that I think warrants a
> 0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of
> other issues that I want finished up and get in before we sp
+1 (non-binding)
BTW, I left a comment on HDFS-4835 suggesting that you include HDFS-3180
for WebHDFS socket connect/read timeouts. It's up to you. (I'm voting +1
for the release plan either way.)
Chris Nauroth
Hortonworks
http://hortonworks.com/
On Fri, May 17, 2013 at 7:25 PM, Eli Collins
+1
On Friday, May 17, 2013, Thomas Graves wrote:
> Hello all,
>
> We've had a few critical issues come up in 0.23.7 that I think warrants a
> 0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of
> other issues that I want finished up and get in before we spin it. Those
> includ
+1
On Sat, May 18, 2013 at 2:40 AM, Thomas Graves wrote:
> Hello all,
>
> We've had a few critical issues come up in 0.23.7 that I think warrants a
> 0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of
> other issues that I want finished up and get in before we spin it. Those
Hello all,
We've had a few critical issues come up in 0.23.7 that I think warrants a
0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of
other issues that I want finished up and get in before we spin it. Those
include HDFS-3875, HDFS-4805, and HDFS-4835. I think those are on t
12 matches
Mail list logo