It seems inevitable that a few annoying regressions will pop up as 0.16.0 becomes more widely deployed, e.g. ARROW-7841 was just reported and patched. I created a 0.16.1 Fix Version in JIRA so that we can tag issues that we may want to cherry pick into a maint-0.16.x branch. We probably would want to wait a couple of weeks before cutting the patch release, though.
Also, as a matter of easing release management for patch releases, I wonder if it makes sense to focus RC verification efforts on the binary artifacts (especially the Python wheels). Should we write down a "reduced" set of tasks for release managers to track for patch releases? Thanks, Wes
