Thanks for chiming in Jon.

I'd like to see the MOB feature included in 1.1, so long as it can be
shipped disabled by default to avoid surprises for unrelated users. That
said, it will depend on contributors' bandwidth to port the patches. Since
Jon is willing, it seems likely that the feature will be included in 1.1.
Maybe you have some bandwidth to help him with the porting efforts?

As for the release subsequent to 1.1, it will be up for the community to
decide, probably sometime around the 3rd quarter of 2015. I haven't heard
any volunteers for 2.0 RM yet, nor for 1.2.

-n

On Mon, Mar 23, 2015 at 3:23 PM, Jonathan Hsieh <[email protected]> wrote:

> Hi Wlim,
>
> I've been running the branch and hope to get it merged into with trunk/
> 2.0.0.  I'd be willing to port it to 1.1 if the release managers will have
> it.  I"m hardening the feature working with Jingcheng and Jiajia.
>
> I've been running integration tests and perf tests against the feature and
> hope to call a merge vote in a few weeks.
>
> Jon.
>
> On Mon, Mar 23, 2015 at 9:17 AM, Wilm Schumacher <
> [email protected]>
> wrote:
>
> > Hi,
> >
> > as this deals with the future releases of hbase, I post it on this list.
> > I think this question goes to the nominated release managers of the 1.1
> > release (thus Nick and Andrew).
> >
> > I'm in desperate need of the MOB feature. I even would rather use a
> > "unstable" release than a recommended without this feature. My plan of
> > releasing my application is around june/july, install at customer a
> > little after that, perhaps august or september.
> >
> > In the thread "Rough goal timelines for 1.1 and 2.0" there Enis wrote
> > that in the 1.1 release the pipelined features (MOB amongst other
> > things) are included and the rough goal is around may. There was no nay,
> > but not a lot of yay either. Furthermore, the JIRA for MOB refers to the
> > 2.0.0 release.
> >
> > Thus my question: is MOB in the 1.1 release coming around may/june? If
> > yes ... never mind ;). Of no, is it planed for the 1.2, or however it
> > will be called, release or should I go with 2.0.0? Is 1.2 even planed?
> > Or is 2.0.0 the next step after 1.1.X? Sean seemed to imply that.
> >
> > Best wishes
> >
> > Wilm
> >
>
>
>
> --
> // Jonathan Hsieh (shay)
> // HBase Tech Lead, Software Engineer, Cloudera
> // [email protected] // @jmhsieh
>

Reply via email to