I have deleted the branch named "4.x-HBase-1.x" as well as the jenkins jobs. I have a local copy of the branch in case we missed something.
I have also updated the jira release versions to be always major.minor.patch format, so 4.4 -> 4.4.0, 4.3 -> 4.3.0, etc. The jira query for whether we have anything only in master looks like we do not need substantial changes: https://issues.apache.org/jira/browse/PHOENIX-1235?jql=project%20%3D%20PHOENIX%20AND%20status%20%3D%20Resolved%20AND%20fixversion%20not%20in%20(4.4.0%2C%204.3.0%2C%204.3.1%2C%204.2.0%2C%204.2.1%2C%204.1.0%2C%204.1.1%2C%204.0.0)%20and%20fixversion%20%3D%205.0.0%20and%20resolution%20%3D%20fixed The question for whether 5.0.0 version in jira should be kept is open. Right now since we have master with target version 4.4.0-SNAPSHOT, we should not have 5.0.0 as target version I think. In this case, I can remove it from jira until we fork again. Phoenix developers, to repeat the plan from the other thread: - We have 4.x-HBase-0.98 with pom.xml version 4.4.0-SNAPSHOT. - Master will also have pom.xml version 4.4.0-SNAPSHOT. But master works with HBase-1.0.x releases. - 4.x-HBase-1.x branch is gone. Please do not push anything there - All commits must go to master and 4.x-HBase-0.98. - Once close to 4.4.0 release, we will fork master and create a branch. - There will be two 4.4.0 releases one for 0.98 and one for 1.0.x (or 1.1.x). Enis On Tue, Mar 31, 2015 at 1:20 PM, Enis Söztutar <enis....@gmail.com> wrote: > Let me do the work. Was waiting for a couple of things on our end. > > Enis > > On Mon, Mar 30, 2015 at 4:51 PM, James Taylor <jamestay...@apache.org> > wrote: > >> As discussed already, we plan to drop the 4.x-HBase-1.x branch as it's >> been determined not to be needed at the present time. Either Enis or I >> will drop this branch by EOD tomorrow. Please let us know if you have >> any concerns. >> Thanks, >> James >> > >
