; > > If there are, what are they, and are they considered blockers?
> > >
> > > Any other reasons not do this ?
> > >
> > > I expect that based on my experience with the master branch, I can do
> > this
> > > in a few days, but I don't wa
t; > > >>>> - Do nothing
> > > >>>> - Move master to HBase 2.2.2
> > > >>>> - Fork master to Hbase-2.0 and Hbase-2.2 branches
> > > >>>> - Build time compatibility modules
> > > >>>> - Run time compa
lper methods which come to contain this common logic. The common class
> >> can remain in the core module. Then all you have in the version specific
> >> modules is scaffolding. In that scaffolding, calls to the static
> methods in
> >> core. It’s not a clever refactor but i
t;>
> >>>>>> The reason that it is not a straightforward decision to merge it is
> >>>> that
> >>>>>> applying that patch breaks compatibility with HBase 2.0.1, the
> current
> >>>>>> base.
> >>>>&
