You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Next »

 

JIRAS requested to be included in 1.2 release after 1.2 branch creation, but before RC roll outs

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.

 

CategoryJIRACurrent StatusCommitter requesting inclusion
Transactions Unable to render Jira issues macro, execution error. patch-availablealangates
HBase Handler Unable to render Jira issues macro, execution error. patch-availableashutoshc
CBO Unable to render Jira issues macro, execution error. patch-availableashutoshc
Logical Optimizer Unable to render Jira issues macro, execution error. patch-availableashutoshc
QL Unable to render Jira issues macro, execution error. patch-availablejdere
    
    
    
    

 

 

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

 

CategoryJIRACurrent Status

Developer/Committer

requesting inclusion

Export/Import Unable to render Jira issues macro, execution error. committedsushanth
Export/Import Unable to render Jira issues macro, execution error. committedsushanth
QL Unable to render Jira issues macro, execution error. committedmmccline
Spark Unable to render Jira issues macro, execution error.

committed

szehon

Types

Unable to render Jira issues macro, execution error.

committed

jdere

QL Unable to render Jira issues macro, execution error. Patch-availablewzheng
QL Unable to render Jira issues macro, execution error. committedvikram.dixit
Metastore Unable to render Jira issues macro, execution error. Patch-availablemithun
Spark Unable to render Jira issues macro, execution error. Patch-availablehari/sushanth
 HCatalog Unable to render Jira issues macro, execution error. In-progresssushanth
JDBC Unable to render Jira issues macro, execution error. Patch-availablehari
HiveServer2 Unable to render Jira issues macro, execution error. Patch-availablehari/thejas
Metastore Unable to render Jira issues macro, execution error. Patch-availablevaibhav
HiveServer2 Unable to render Jira issues macro, execution error. Patch-availablevaibhav
HiveServer2 Unable to render Jira issues macro, execution error. Patch-availablevaibhav
ACID Unable to render Jira issues macro, execution error. Patch-availableEugene
ACID Unable to render Jira issues macro, execution error.  Eugene
ACID Unable to render Jira issues macro, execution error.  Eugene
Security Unable to render Jira issues macro, execution error.  mithun
Security Unable to render Jira issues macro, execution error.  mithun
Authorization Unable to render Jira issues macro, execution error.  mithun
HCatalog Unable to render Jira issues macro, execution error.  mithun
HCatalog Unable to render Jira issues macro, execution error.  mithun
Replication Unable to render Jira issues macro, execution error.  sushanth
QL Unable to render Jira issues macro, execution error.  sushanth
Parkquet Unable to render Jira issues macro, execution error. Patch availableFerdinand Xu

 

Intended Release Timeline

 

00:01, Saturday, 25th Apr 2015 PDT : Deadline for call for patches for general purpose feature inclusion.(must have patch-available already to request for feature inclusion after this)

00:15, Saturday, 25th Apr 2015 PDT : Branch creation for branch-1.2.

12:01, Monday 27th Apr 2015 PDT : Work begins on rolling out RC0 - the purpose of RC0 will be to test out that we're able to go through the process of making a release candidate, and will likely not include all the bugfixes planned for this release.

00:01, Tuesday, 28th Apr 2015 PDT : Deadline for call for patches for feature inclusion if the features are near end-of-development. (only bugfixes allowed after this)

12:01, Wednesday, 29th Apr 2015 PDT : Current tracking time for community availability of RC0.

15:01, Thursday, 30th Apr 2015 PDT : Deadline for call for patches for inclusion for bugfixes that have a workaround (only critical bugfixes that do not have workarounds allowed after this), intended deadline for committing all feature request patches.

16:01, Thursday, 30th Apr 2015 PDT : Work begins on rolling out RC1 - the purpose of RC1 will be to be the first actual release candidate, and include all the feature commits and any bugfix commits that have happened so far. Full test run intended on RC1, with community verification.

16:01, Friday, 1st May 2015 PDT : Current tracking time for community availability of RC1.

 

  • No labels