That sounds good to me.
On Tue, Jun 26, 2018 at 11:49 AM, Thejas Nair wrote:
> Hi Vihang,
> I don't think we need to serialize these releases at this time. The
> metastore is still being released as part of hive as well at this
> time.
> Maybe as part of the Hive 3.1 release process, ie after br
Hello,
Branch for 3.1 release has been cut off (branch-3.1). I’ll update all the jiras
currently targeted for 3.1 to defer it to next release. Please do not commit
anything to branch-3.1.
Thanks,
Vineet
> On Jun 26, 2018, at 11:49 AM, Thejas Nair wrote:
>
> Hi Vihang,
> I don't think we need
Hi Vihang,
I don't think we need to serialize these releases at this time. The
metastore is still being released as part of hive as well at this
time.
Maybe as part of the Hive 3.1 release process, ie after branching,
during stabilization/voting you can verify that metastore in
standalone mode is w
+1 for releasing Hive 3.1. I can be the RM for the metastore 3.1 release
while Vineet takes care of the Hive release. The metastore will be released
from branch-3.1 after it is cut out. I propose to make a metastore 3.1
release first and then release Hive 3.1 shortly afterwards so that it
depends o
I think it would be useful to do a metastore 3.1 release as well along with
the release. In order to do that we should deploy metastore in standalone
mode, make sure it works as expected and also document how to install and
use metastore as a standalone module.
On Mon, Jun 25, 2018 at 3:00 PM, Vin
