Re: Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha

2013-06-01 Thread Konstantin Boudnik
I changes are completed, I have updated branch-2 and trunk CHANGES.txt files as planned. Version of the branch-2 is set to 2.1.0-beta; 2.0.5-alpha release artifacts are deployed to the staging area. Thanks for your patience, guys! Cos On Fri, May 31, 2013 at 12:45PM, Konstantin Boudnik wrote: >

Re: Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha

2013-05-31 Thread Azuryy Yu
2.1.0-alpha is 2.0.5-beta actually. --Send from my Sony mobile. On Jun 1, 2013 8:14 AM, "Ted Yu" wrote: > I am currently testing HBase 0.95 using 2.0.5-SNAPSHOT artifacts. > > Would 2.1.0-SNAPSHOT maven artifacts be available after tomorrow's change ? > > Thanks > > On Fri, May 31, 2013 at 12:45

Re: Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha

2013-05-31 Thread Ted Yu
I am currently testing HBase 0.95 using 2.0.5-SNAPSHOT artifacts. Would 2.1.0-SNAPSHOT maven artifacts be available after tomorrow's change ? Thanks On Fri, May 31, 2013 at 12:45 PM, Konstantin Boudnik wrote: > Guys, > > I will be performing some changes wrt to moving 2.0.4.1 release candidate

Re: Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha

2013-05-31 Thread Konstantin Boudnik
Indeed! The second part is happening on Saturday, JUN01 2013 1PM-2PM PST. On Fri, May 31, 2013 at 01:01PM, Alejandro Abdelnur wrote: > Cos, just to be clear, this is happening SAT JUN01 1PM-2PM PST, not now > (FRI MAY31 1PM PST). Correct? > > Thx > > On Fri, May 31, 2013 at 12:45 PM, Konstantin

Re: Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha

2013-05-31 Thread Alejandro Abdelnur
Cos, just to be clear, this is happening SAT JUN01 1PM-2PM PST, not now (FRI MAY31 1PM PST). Correct? Thx On Fri, May 31, 2013 at 12:45 PM, Konstantin Boudnik wrote: > Guys, > > I will be performing some changes wrt to moving 2.0.4.1 release candidate > to > 2.0.5 space. As outline below by Ale

Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha

2013-05-31 Thread Konstantin Boudnik
Guys, I will be performing some changes wrt to moving 2.0.4.1 release candidate to 2.0.5 space. As outline below by Alejandro: 1. I will create new 2.0.5-alpha branch from the current head of 2.0.4-alpha that contains 2.0.4.1 changes 2. consequently, set the artifacts version on the new branch to