Hi,
Under the umbrella of HBASE-20951, we had initial said that we'd start
landing code changes on a feature branch when we get there. Sergey S
asked the good question to me the other day: "why a feature branch and
not master?"
Honestly, I don't have a good answer. The goal in implementation is to
move incrementally and not leave things "broken" when possible. Assuming
that we can do that, using a feature branch would just create pain on
the eventual merge back to master.
Do folks have strong feelings here? Is using master better to prevent
review "debt" from piling up when the merge-vote comes? Or, do people
foresee an HBase 3 in the works before this work would be done (sometime
in 2019)?
Would like to hear your input.
- Josh
