Thanks Sangjin for finding this.
> It looks like hadoop-cloud-storage-project was missed in the version set?
Yes. Probably this is because
hadoop-cloud-storage-project
is missing in pom.xml so `mvn versions:set` did not work for the
project. Filed HADOOP-14004 for fixing this.
Regards,
Ak
It looks like hadoop-cloud-storage-project was missed in the version set?
On Thu, Jan 19, 2017 at 4:19 PM, Andrew Wang
wrote:
> I've branched branch-3.0.0-alpha2 and moved out the target versions except
> for our last blocker to a new 3.0.0-alpha3 version.
>
> Business can continue as usual, ple
I've branched branch-3.0.0-alpha2 and moved out the target versions except
for our last blocker to a new 3.0.0-alpha3 version.
Business can continue as usual, please just set target/fix versions of
3.0.0-alpha3 now instead of 3.0.0-alpha2.
Thanks,
Andrew
On Thu, Jan 19, 2017 at 3:52 PM, Andrew W
Heads up that I'm branching for 3.0.0-alpha2 and moving out targets
versions. We're waiting on one last blocker which is in final stages of
review.
Best,
Andrew
On Wed, Jan 4, 2017 at 11:15 AM, Andrew Wang
wrote:
> Hi folks,
>
> Thanks to the hard work of many contributors, we've been steadily
Hi folks,
Thanks to the hard work of many contributors, we've been steadily burning
down alpha2 blockers. There are only 4 remaining, three of which are PA and
likely to be committed shortly.
Once those three go in (hopefully this week), I'm going to cut the alpha2
branch and wait for that last b
Hi folks,
It's been a month since 3.0.0-alpha1, and we've been incorporating fixes
based on downstream feedback. Thus, it's getting to be time for
3.0.0-alpha2. I'm using this JIRA query to track open issues:
https://issues.apache.org/jira/issues/?jql=project%20in%20(HADOOP%2C%20HDFS%2C%20MAPREDU
