DB install and upgrade scripts in the brave new world of multiple release lines

[Alan Gates <al...@gmail.com>]

The change to have branches running with master as 4 and branch-3 for 3.x
releases is complicating our DB install and upgrade scripts.  There's a
JIRA to track the changes but some discussion on that JIRA of how best to
proceed, starting with the comment
https://issues.apache.org/jira/browse/HIVE-19323?focusedCommentId=16489833&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16489833
I'm posting this here as others may be interested in chiming in.

Alan.

Re: DB install and upgrade scripts in the brave new world of multiple release lines

[Vihang Karajgaonkar <vi...@cloudera.com>]

Historically speaking, once we cut out a branch for a certain release line,
most of the development shifts to master and only critical bug fixes are
made in release specific branches. This happened when branch-2 was cut out
too. Fortunately (or not) we always have had some minor releases on the
latest releases before the next major release was announced. This kept the
linearity of the upgrade process. Assuming the same trend is going to
repeat i.e master being the active development branch and only critical
fixes going to branch-3 (with branch-2 being ignored?) we should keep the
upgrade path of 3.max -> 4.0 open. Otherwise we will end up with weird 3.x
releases which can only be upgraded to 4.1 and so on.

On Thu, May 24, 2018 at 2:33 PM, Alan Gates <al...@gmail.com> wrote:

> The change to have branches running with master as 4 and branch-3 for 3.x
> releases is complicating our DB install and upgrade scripts.  There's a
> JIRA to track the changes but some discussion on that JIRA of how best to
> proceed, starting with the comment
> https://issues.apache.org/jira/browse/HIVE-19323?
> focusedCommentId=16489833&page=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel#comment-16489833
> I'm posting this here as others may be interested in chiming in.
>
> Alan.
>