Good idea and +1.
Thanks
Stephen
On Sun, Apr 10, 2016 at 7:12 PM, ramkrishna vasudevan <
ramkrishna.s.vasude...@gmail.com> wrote:
> +1
>
> On Mon, Apr 11, 2016 at 4:30 AM, Gerry Morales
> wrote:
>
> > unsubscribe
> >
> > On Thu, Apr 7, 2016 at 9:18 PM, Stack
+1
On Mon, Apr 11, 2016 at 4:30 AM, Gerry Morales
wrote:
> unsubscribe
>
> On Thu, Apr 7, 2016 at 9:18 PM, Stack wrote:
>
> > Any objection?
> >
> > jdk7 is dead, EOL'd.
> >
> > You all good w/ this?
> >
> > St.Ack
> >
>
unsubscribe
On Thu, Apr 7, 2016 at 9:18 PM, Stack wrote:
> Any objection?
>
> jdk7 is dead, EOL'd.
>
> You all good w/ this?
>
> St.Ack
>
Thanks all for chiming in. I filed HBASE-15624 Move master
branch/hbase-2.0.0 to jdk-8 only to act on the decision made here.
St.Ack
On Fri, Apr 8, 2016 at 11:30 AM, Yu Li wrote:
> +1
>
> Best Regards,
> Yu
>
> On 9 April 2016 at 02:13, Stack wrote:
>
> > I
+1
Best Regards,
Yu
On 9 April 2016 at 02:13, Stack wrote:
> I filed https://issues.apache.org/jira/browse/YETUS-369 (though I hate
> filing stuff w/o putting up a patch... maybe I'll get to doing one!)
> St.Ack
>
> On Fri, Apr 8, 2016 at 6:04 AM, Sean Busbey
I filed https://issues.apache.org/jira/browse/YETUS-369 (though I hate
filing stuff w/o putting up a patch... maybe I'll get to doing one!)
St.Ack
On Fri, Apr 8, 2016 at 6:04 AM, Sean Busbey wrote:
> I don't think there's an issue yet.
> On Apr 8, 2016 00:12, "Stack"
+1
-Mikhail
On Fri, Apr 8, 2016 at 10:18 AM, Esteban Gutierrez
wrote:
> +1
>
> --
> Cloudera, Inc.
>
>
> On Fri, Apr 8, 2016 at 8:36 AM, Nick Dimiduk wrote:
>
> > +1
> >
> > On Thursday, April 7, 2016, Stack wrote:
> >
> > > Any
+1
--
Cloudera, Inc.
On Fri, Apr 8, 2016 at 8:36 AM, Nick Dimiduk wrote:
> +1
>
> On Thursday, April 7, 2016, Stack wrote:
>
> > Any objection?
> >
> > jdk7 is dead, EOL'd.
> >
> > You all good w/ this?
> >
> > St.Ack
> >
>
+1
On Thursday, April 7, 2016, Stack wrote:
> Any objection?
>
> jdk7 is dead, EOL'd.
>
> You all good w/ this?
>
> St.Ack
>
I don't think it'll actually speed up tests much. In precommit we only
check one jdk for unit tests and in postcommit we do them in parallel.
On Apr 8, 2016 03:44, "Elliott Clark" wrote:
> As a side benefit, only testing one jdk would seriously speed up test runs.
>
> +1
>
>
I don't think there's an issue yet.
On Apr 8, 2016 00:12, "Stack" wrote:
> Is there a YETUS issue for this Sean or should I file one?
> St.Ack
>
> On Thu, Apr 7, 2016 at 9:21 PM, Sean Busbey wrote:
>
> > we'll need to get a feature into yetus that can
+1 on jdk8 only. Bunch of code could be refactored with jdk8's new
features, new classes and new methods.
For example, most 'get->putIfAbsent->checkAndCleanUp' and 'get->lock->get
again->put->unlock' can be replaced by computeIfAbsent.
2016-04-08 16:43 GMT+08:00 Elliott Clark :
As a side benefit, only testing one jdk would seriously speed up test runs.
+1
On Thu, Apr 7, 2016 at 10:12 PM, Stack wrote:
> Is there a YETUS issue for this Sean or should I file one?
> St.Ack
>
> On Thu, Apr 7, 2016 at 9:21 PM, Sean Busbey wrote:
>
>
Is there a YETUS issue for this Sean or should I file one?
St.Ack
On Thu, Apr 7, 2016 at 9:21 PM, Sean Busbey wrote:
> we'll need to get a feature into yetus that can change multijdk
> settings by branch, presuming that change will result in us either
> taking on jdk8-only
we'll need to get a feature into yetus that can change multijdk
settings by branch, presuming that change will result in us either
taking on jdk8-only dependencies or direct use of jdk8-only features.
On Thu, Apr 7, 2016 at 9:18 PM, Stack wrote:
> Any objection?
>
> jdk7 is
Any objection?
jdk7 is dead, EOL'd.
You all good w/ this?
St.Ack
16 matches
Mail list logo