Would it simplify the cross-project commit process if we actually always depended on the snapshot on master/etc., and only switched to a particular version of storage-api in release branches? If there are unreleased storage-api changes when Hive is being released that are needed for the release, they’d be released all together just before the Hive release, if needed.
On 17/1/1, 10:19, "Owen O'Malley" <omal...@apache.org> wrote: >Hi all, > As we discussed back in >https://mid.mail-archive.com/dev@hive.apache.org/msg121112.html . I'd like >to make a release of storage-api. I've written up a proposal at >https://cwiki.apache.org/confluence/display/Hive/Storage+API+Release+Propo >sal >and the patch for HIVE-15419 is pretty close. Once HIVE-15419 is >committed, >I'd like to cut a branch (eg storage-branch-2.2) and make a release >candidate (eg. storage-release-2.2.0rc0). > >Any concerns? > >Thanks, > Owen
