Intended Release Timeline

Last phase of JIRAs for inclusion to 1.2 release (list open for product outages, regressions and trivial patches)

Requirement : Product outages (critical bugfixes without workarounds), Regressions (bugs discovered during testing - usecases that used to work with prior hive releases) or Trivial patches (requiring no re-testing) only. Release Blockers, such as running afoul of Apache release guidelines are also acceptable as related to outages.

Deadline for inclusion :  Till the final RC gets voted on and accepted

Status : Open for inclusion, but restricted on type of issue

List of JIRAs for 1.2.1

This is to be a list of jiras that were initially intended for 1.2, but cannot be finished in time for 1.2.0, and are not blockers/outages but desired in 1.2 nonetheless. These will be accepted as part of the RC process if they get done by then, but will not be considered release blockers. If 1.2.0 releases without them, they'll be on track for 1.2.1.

Rules for inclusion into branch-1.2 targeting 1.2.2

Now that 1.2.1 has been released, branch-1.2 now tracks an eventual 1.2.2 release. To commit any patch to branch-1.2 now, the following rules apply:

1. The commit must not introduce any schema or interface changes.
2. The commit must fix a bug that causes an outage/breakage (such as an NPE) in regular hive operation, or it must fix a data corruption issue or it must be a security fix with an appropriate CVE.

All commits that do not meet these criteria should be directed towards branch-1 (for an eventual 1.3 release). The goal of an eventual 1.2.2 update to branch-1.2 is merely to ensure that there is a stable maintenance line to use, and should not be used to simply add additional features to previously released lines.

Committed JIRAS in branch-1.2 for potential 1.2.2

Committed JIRAS in branch-1.2 for 1.2.1

(split out into a separate wikipage to speed up loading this page)

List of JIRAS deferred out of 1.2

The following are jiras originally intended for branch-1.2, but at this time, should not be committed to branch-1.2, and should only go to master(1.3). These jiras were moved out of the above backlog list into this after a discussion between the RM and the committer asking for inclusion.

...

JIRAS requested to be included in 1.2 release after RC0 preparation begins (list now closed)

Requirement : Bugfixes only

Deadline for inclusion :  00:01, Friday, 1st May 2015 PDT

Status : List frozen

JIRAS requested to be included in 1.2 release after 1.2 branch creation, but before RC0 roll outs (list now closed)

Requirement : To add a JIRA to to this list, the JIRA must be in a patch-available state or committed state for trunk (or JIRA must be a minimal port for branch-1.2 alone), and must not be a "large feature", where "large feature" is defined as something that changes api, changes db schema, or carries significant testing risk. Bugfixes are unrestricted at this time.

Deadline for inclusion :  00:01, Tuesday, 28th Apr 2015 PDT

Status :  List frozen, all jiras in this list will be honoured for inclusion to Hive 1.2 and are approved for commit to branch-1.2.

JIRAS requested to be included in 1.2 release before 1.2 branch creation (list now closed)

Requirement : General purpose feature jiras or bugfixes. 

Deadline for inclusion :  00:01, Saturday, 25th Apr 2015 PDT

Status: List frozen, all jiras in this list will be honoured for inclusion to Hive 1.2 and are approved for commit to branch-1.2.

...

Committed JIRAS in branch-1.2 for 1.2.0

(split out into a separate wikipage to speed up loading this page)

...