Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns;
	h=received:user-agent:date:subject:from:to:message-id:
	thread-topic:thread-index:in-reply-to:mime-version:content-type:
	content-transfer-encoding:x-originalarrivaltime;
	b=mVihoLhU5g8DFOeXeIVi9p3ArU3/tI+ZBTGUboo12sydiziBq9NRvoxAvEzK13VX
User-Agent: Microsoft-Entourage/12.23.0.091001
Date: Wed, 24 Feb 2010 10:31:26 -0800
Subject: Re: [VOTE] Avro release 1.3.0 (rc 2)
From: Scott Banachowski <sbanacho@yahoo-inc.com>
To: avro-dev <avro-dev@hadoop.apache.org>, Doug Cutting <cutting@apache.org>
Message-ID: <C7AAB07E.3A839%sbanacho@yahoo-inc.com>
Thread-Topic: [VOTE] Avro release 1.3.0 (rc 2)
Thread-Index: Acq1f5KwLKqEZSOpPUe0zpM/+1ABLg==
In-Reply-To: <4B846A7A.90700@apache.org>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

+1
"build.sh dist" looks fine to me.

"build.sh test" seems to fail for interop tests, but I suspect it's my
environment and haven't had a chance to investigate why.  I assume others
would have flagged this otherwise.

I also notice that the interop tests run the whole configure/build chain for
C again (instead of re-using the build that was created from the previous
unit tests).  Is that intentional?


Scott


On 2/23/10 3:53 PM, "Doug Cutting" said:

> I have created a third candidate build for Avro release 1.3.0.
> 
> Please download, test, and vote by 26 February.
> 
> http://people.apache.org/~cutting/avro-1.3.0-rc2/
> 
> Thanks,
> 
> Doug