Tom White helped me figure it out, and closed the Nexus repository for me.
Thanks Tom for helping and Stack for offering to help.
On Fri, Aug 1, 2014 at 11:28 AM, Karthik Kambatla
wrote:
> Folks,
>
> I think we are very close to voting on RC0. Just wanted to check one
> (hopefully) last thing.
Folks,
I think we are very close to voting on RC0. Just wanted to check one
(hopefully) last thing.
I am unable to verify the signed maven artifacts are actually deployed. To
deploy the artifacts, I did the following and it looked like it ran fine.
1. .m2/settings.xml -> server-id is apache.s
Thanks to Andrew's patch on HADOOP-10910, I am able to build an RC.
On Wed, Jul 30, 2014 at 1:59 AM, Ted Yu wrote:
> Adding bui...@apache.org
>
> Cheers
>
> On Jul 30, 2014, at 12:52 AM, Andrew Wang
> wrote:
>
> > Alright, dug around some more and I think it's that FINDBUGS_HOME is not
> > bei
Adding bui...@apache.org
Cheers
On Jul 30, 2014, at 12:52 AM, Andrew Wang wrote:
> Alright, dug around some more and I think it's that FINDBUGS_HOME is not
> being set correctly. I downloaded and extracted Findbugs 1.3.9, pointed
> FINDBUGS_HOME at it, and the build worked after that. I don't k
Alright, dug around some more and I think it's that FINDBUGS_HOME is not
being set correctly. I downloaded and extracted Findbugs 1.3.9, pointed
FINDBUGS_HOME at it, and the build worked after that. I don't know what's
up with the default maven build, it'd be great if someone could check.
Can some
I looked in the log, it also looks like findbugs is OOMing:
[java] Exception in thread "main" java.lang.OutOfMemoryError: GC
overhead limit exceeded
[java] at edu.umd.cs.findbugs.ba.Path.grow(Path.java:263)
[java] at edu.umd.cs.findbugs.ba.Path.copyFrom(Path.java:113)
[
Devs,
I created branch-2.5.0 and was trying to cut an RC, but ran into issues
with creating one. If anyone knows what is going on, please help me out. I
ll continue looking into it otherwise.
https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/24/console
is the build that failed. It a
I've just committed YARN-2247, which is the last 2.5 blocker from YARN.
On Sat, Jul 26, 2014 at 5:02 AM, Karthik Kambatla
wrote:
> A quick update:
>
> All remaining blockers are on the verge of getting committed. Once that is
> done, I plan to cut a branch for 2.5.0 and get an RC out hopefully
A quick update:
All remaining blockers are on the verge of getting committed. Once that is
done, I plan to cut a branch for 2.5.0 and get an RC out hopefully this
coming Monday.
On Fri, Jul 25, 2014 at 12:32 PM, Andrew Wang
wrote:
> One thing I forgot, the release note activities are happening
One thing I forgot, the release note activities are happening at
HADOOP-10821. If you have other things you'd like to see mentioned, feel
free to leave a comment on the JIRA and I'll try to include it.
Thanks,
Andrew
On Fri, Jul 25, 2014 at 12:28 PM, Andrew Wang
wrote:
> I just went through an
I just went through and fixed up the HDFS and Common CHANGES.txt for 2.5.0.
As a friendly reminder, please try to put things under the correct section
:) We have subsections for the xattr changes in HDFS-2006 and HADOOP-10514,
and there were some unrelated JIRAs appended to the end.
I'd also enco
Hi Wangda,
The following link is same link as Karthik mentioned:
https://issues.apache.org/jira/browse/YARN-2247?jql=project%20in%20(Hadoop%2C%20HDFS%2C%20YARN%2C%20%22Hadoop%20Map%2FReduce%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20%22Target%20Version%2Fs%22%20%3D%202.5.0%20AND%20priority
I raised YARN-2247 as the blocker of 2.5.0.
On Thu, Jul 17, 2014 at 9:42 AM, Wangda Tan wrote:
> Hi Karthik,
> I found I cannot access the filter: http://s.apache.org/vJg. Could you
> please check its permission? I'd like to know if there's any related issues
> to me. :)
>
> Thanks,
> Wangda
>
We are down to 4 blockers and looks like they are all actively being worked
on. Please reconsider marking new JIRAs as blockers.
Thanks
Karthik
PS: I moved out a couple of JIRAs that didn't seem like true blockers to
2.6.
On Wed, Jul 9, 2014 at 11:43 AM, Karthik Kambatla
wrote:
> Folks,
>
> W
Folks,
We have 10 blockers for 2.5. Can the people working on them revisit and see
if they are really blockers. If they are, can we try to get them in soon?
It would be nice to get an RC out the end of this week or at least early
next week?
Thanks
Karthik
On Wed, Jul 2, 2014 at 11:32 PM, Karthi
I just
1. moved non-blocker 2.5 JIRAs to 2.6.
2. created branch-2.5 and added sections for 2.6.0 in all CHANGES.txt in
trunk and branch-2.
3. Will create branch-2.5.0 when we are ready to create an RC
There are 11 pending blockers for 2.5.0: http://s.apache.org/vJg
Committers - please exercise ca
16 matches
Mail list logo
