If the underlying problem is lack of reviewers for these improvements, how about a design doc giving some motivation for the improvements and explaining how they'll be implemented? Then we can decide if a branch or a few JIRAs on trunk makes more sense.
The description for HADOOP-12857 is just "let's rework this to be smarter" which could be the description of any JIRA in Hadoop (except for the ones which make things dumber, of course). best, Colin On Tue, Mar 22, 2016, at 11:23, Andrew Wang wrote: > A branch sounds fine, but how are we going to get 3 +1's to merge it? If > it's hard to find one reviewer, seems even harder to find two. > > On Tue, Mar 22, 2016 at 10:56 AM, Allen Wittenauer < > allenwittena...@yahoo.com.invalid> wrote: > > > > > > On Mar 22, 2016, at 10:49 AM, larry mccay <larry.mc...@gmail.com> wrote: > > > > > > That sounds like a reasonable approach and valid use of branches to me. > > > > > > Perhaps a set of functional tests could be provided/identified that would > > > help the review process by showing backward compatibility along with new > > > extensions for things like dynamic commands? > > > > > > > This is going into trunk, so no need for backward compatibility. > >
