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.

...

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.

...

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

Requirement : Bugfixes only

...

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.

...

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

Requirement : General purpose feature jiras or bugfixes. 

...