phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1642) Make Phoenix Master Branch pointing to HBase1.0.0
Date Tue, 03 Mar 2015 03:01:04 GMT


Enis Soztutar commented on PHOENIX-1642:

I have pushed 1.0.1-SNAPSHOT to the maven snapshot repositories BTW. You can depend on it
for the failed unit test. Once 1.0.1 is released, we can then change it to be 1.0.1 and drop
the snapshot. 

For the branches, I like the model of having phoenix releases with the same set of features,
but for different versions of HBase. It may mean 1 branch per supported HBase branch if we
are not doing shims.
Whether use 5.x or 4.x-hbase-1.0 is a matter of how frequent we want to bump major versions
I think. HBase is expected to release 1.1, 1.2, etc and even in best case, I expect some minor
changes that may need a shim or a different branch between 1.x releases. 

> Make Phoenix Master Branch pointing to HBase1.0.0
> -------------------------------------------------
>                 Key: PHOENIX-1642
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>         Attachments: PHOENIX-1642.patch
> As HBase1.0.0 will soon be released, the JIRA is to point Phoenix master branch to HBase1.0.0
release. Once we reach consensus,  we could also port the changes into Phoenix 4.0 branch
as well which can be done in a separate JIRA.

This message was sent by Atlassian JIRA

View raw message