l jiras after the original merge - https://goo.gl/6stN7Y - we
> > need to make sure if these are the only ones relevant.
> >
> > From: Jonathan Hsieh <j...@cloudera.com>
> > Sent: Wednesday, March 02, 2016 2:03 PM
> > To: dev@hbase.apache.or
o make sure if these are the only ones relevant.
>
> From: Jonathan Hsieh <j...@cloudera.com>
> Sent: Wednesday, March 02, 2016 2:03 PM
> To: dev@hbase.apache.org
> Subject: Re: MOB in branch-1? (Re: [RESULT][VOTE] Merge branch hbase-11339
> HBas
Wednesday, March 02, 2016 2:03 PM
To: dev@hbase.apache.org
Subject: Re: MOB in branch-1? (Re: [RESULT][VOTE] Merge branch hbase-11339
HBase MOB to trunk)
I'll offer what I think would be another reasonable and likely less
destabilizing approach: essentially treat it as a branch. We could start
f
t;> failures on master to do with MOB are really MOB related or something
> > else
> > >>> (for argument's sake, let's say, procv2)..
> > >> Sounds like we need to spend a bit of time digging in on the flakey
> > tests
> > >> then. Branch-1 is pre
; >> Sounds like we need to spend a bit of time digging in on the flakey
> tests
> >> then. Branch-1 is pretty stable now after a bunch of expended effort by
> a
> >> few folks. Would be a pity taking a step back.
> >>
> >> St.Ack
> >>
> &g
we need to spend a bit of time digging in on the flakey tests
>> then. Branch-1 is pretty stable now after a bunch of expended effort by a
>> few folks. Would be a pity taking a step back.
>>
>> St.Ack
>>
>>
>>
>>> On the point about the DISCUSS thread, ye
yeah, it's fine to do it if folks
>> feel it's the right way to go.
>> ____
>> From: saint....@gmail.com <saint....@gmail.com> on behalf of Stack <
>> st...@duboce.net>
>> Sent: Wednesday, March 02, 2016 10:55 AM
>> To: HB
saint@gmail.com <saint@gmail.com> on behalf of Stack <
> st...@duboce.net>
> Sent: Wednesday, March 02, 2016 10:55 AM
> To: HBase Dev List
> Subject: Re: MOB in branch-1? (Re: [RESULT][VOTE] Merge branch hbase-11339
> HBase MOB to trunk)
>
> (Doing anothe
int@gmail.com> on behalf of Stack
<st...@duboce.net>
Sent: Wednesday, March 02, 2016 10:55 AM
To: HBase Dev List
Subject: Re: MOB in branch-1? (Re: [RESULT][VOTE] Merge branch hbase-11339
HBase MOB to trunk)
(Doing another resend...)
I have objection to you, Ted Yu, doing it. MOB has spre
(Doing another resend...)
I have objection to you, Ted Yu, doing it. MOB has spread all about master
branch. Backport should be done by someone who knows MOB.
Higher up in this thread, Sean asks: "Can we get a [DISCUSS] flagged thread
to see what, if anything, folks
would like to see gate
On Mon, Feb 29, 2016 at 6:56 PM, Jonathan Hsieh wrote:
> ...
> We've been working on trying to get at least one of them to present at
> hbasecon, but I'm not reviewing submissions this year and don't know if
> they made it or not.
>
> This did not happen. The use case is to
om>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hello, guys, the MOB is in master branch. I saw bug fixes
>>>>>>>>>> happening
>>
aid
>>>>>>>>>>>>>> if we don't do it now, it would be harder in the future to
>>>> back
>>>>>>>>> port
>>>>>>>&
t; > >> >>>>>>>> When I'm back in the office I'll check out master and
> have
> > a
> > > > >> >> look
> > > > >> >>>> into
> > > > >> >>>&g
>> >>>>>>> any
> > > >> >>>>>>>> locally repeatable test failures. Anyway in my opinion at
> > this
> > > >> >>>> point it
> > > >> >>>>>>>> would make the most sense for us to keep the MOB changes in
> > on
> > > >> >>>
gt; >>>> master
> > >> >>>>>> and
> > >> >>>>>>>> deal with any fallout in follow on issues. I think all who
> > voted
> > >> >>> +1
> > >> >>>> for
> > >> >>>>>>>> this chan
uld be good!
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> On Wed, Jul 22, 2015 at 8:09 PM, Jonathan Hsieh <
>> >> j...@cloudera.com
>> >>>>
>> >>>>>>> wrote:
&g
't think mob is responsible for these failures.
>>>>>>>>>
>>>>>>>>> Jon.
>>>>>>>>>
>>>>>>>>> On Wed, Jul 22, 2015 at 4:32 PM, Jonathan Hsieh <
>>> j...@clouder
t;> > > > > something hung along the way, and that most of the previous
> > > builds
> > > >> > had
> > > >> > > > > failed for various reasons. :(
> > > >> > > > >
> > > >> > > >
gt;>>>>>
> >>>>>>>>> I had two clean full builds/unit test on my internal setup and
> >>> the
> >>>>>>> latest
> >>>>>>>>> build went back to ~4325 total tests and failures on Procedure
> >>>>
j...@cloudera.com
> > >>>>
> > >>>>>>> wrote:
> > >>>>>>>>
> > >>>>>>>>> I had two clean full builds/unit test on my internal setup and
> > >>> the
> > >>&g
Jingcheng and thanks to all who have been involved with reviews,
> > > > >> discussion, and voting!
> > > > >>
> > > > >> Jon
> > > > >>
> > >
6 PM, Jonathan Hsieh <j...@cloudera.com>
>> > > > wrote:
>> > > > >
>> > > > >> I've merged the code in to master. Thanks for all the hard work
>> > > >
; > > we'll
> >> > > > > take hunt it down and take care of it.
> >> > > > >
> >> > > > > Jon.
> >> > > > >
> >> > > > > [1] https://builds.apache.org/job/HBase-TRUNK/6672/
> >> > > > >
&g
> builds
> > >> > had
> > >> > > > > failed for various reasons. :(
> > >> > > > >
> > >> > > > > I kicked it off again have it do another try. If it is mob
> > related
> > >> > &g
> > >> > > > > the first full build after the merge [1] failed. It looked
> > like
> > > >> > > > > something hung along the way, and that most of the previous
> > > builds
> > > >> > had
> > > >
eng Du <
> > jingcheng...@intel.com>
> > > >> wrote:
> > > >>
> > > >>> Hi all,
> > > >>>
> > > >>> The vote passes with 8 +1s and no -1. Thanks all for guiding,
> helping
> > > and
> >
!
>> > >>
>> > >> Jon
>> > >>
>> > >> On Wed, Jul 22, 2015 at 12:45 AM, Jingcheng Du <
>> jingcheng...@intel.com>
>> > >> wrote:
>> > >>
>> > >>> Hi all,
>>
t; The vote passes with 8 +1s and no -1. Thanks all for guiding, helping
> > and
> > >>> voting!
> > >>> We will work on the merge activities and will let guys know about the
> > >>> detailed plan for merge time.
> > >>> And tha
on the merge activities and will let guys know about the
detailed plan for merge time.
And thanks Jon for helping merge this branch to trunk!
Regards,
Jingcheng
--
View this message in context:
http://apache-hbase.679495.n3.nabble.com/RESULT-VOTE-Merge-branch-hbase-11339-HBase
-VOTE-Merge-branch-hbase-11339-HBase-MOB-to-trunk-tp4073446.html
Sent from the HBase Developer mailing list archive at Nabble.com.
--
// Jonathan Hsieh (shay)
// HBase Tech Lead, Software Engineer, Cloudera
// j...@cloudera.com // @jmhsieh
in context:
http://apache-hbase.679495.n3.nabble.com/RESULT-VOTE-Merge-branch-hbase-11339-HBase-MOB-to-trunk-tp4073446.html
Sent from the HBase Developer mailing list archive at Nabble.com.
!
We will work on the merge activities and will let guys know about the
detailed plan for merge time.
And thanks Jon for helping merge this branch to trunk!
Regards,
Jingcheng
--
View this message in context:
http://apache-hbase.679495.n3.nabble.com/RESULT-VOTE-Merge-branch-hbase-11339-HBase
will work on the merge activities and will let guys know about the
detailed plan for merge time.
And thanks Jon for helping merge this branch to trunk!
Regards,
Jingcheng
--
View this message in context:
http://apache-hbase.679495.n3.nabble.com/RESULT-VOTE-Merge-branch-hbase-11339-HBase
,
Jingcheng
--
View this message in context:
http://apache-hbase.679495.n3.nabble.com/RESULT-VOTE-Merge-branch-hbase-11339-HBase-MOB-to-trunk-tp4073446.html
Sent from the HBase Developer mailing list archive at Nabble.com.
--
// Jonathan Hsieh (shay)
// HBase Tech Lead, Software Engineer
and
voting!
We will work on the merge activities and will let guys know about the
detailed plan for merge time.
And thanks Jon for helping merge this branch to trunk!
Regards,
Jingcheng
--
View this message in context:
http://apache-hbase.679495.n3.nabble.com/RESULT-VOTE-Merge-branch-hbase
36 matches
Mail list logo