Folks, Over the last couple of weeks, we have had several changes (both merged and in the pipeline) as follow-up work after ARROW-1463 was merged.
I feel that refactoring suggestions are being proposed on-the-fly while the developer is already in progress with the code changes and it's too late to have an opinion on the changes. It doesn't give the reviewer enough time to understand the rationale behind the proposed changes and assess its impact downstream and most importantly have a clear idea of what all changes are being implemented so that downstream consumers can understand what to expect when they rebase next time. Two sets of such follow up changes are already merged to master. For the ones in pipeline, I request people to send out a doc or spec highlighting what we are proposing to change and rationale similar to how requirements and design spec for ARROW-1463 was sent out prior to making any code changes. Thanks, Siddharth
