I have created a candidate build for Avro release 1.3.1.

Changes are listed at:

   http://tinyurl.com/avro131

Please download, test, and vote by 16 March.

   http://people.apache.org/~cutting/avro-1.3.1-rc0/

Thanks,

Doug

Have you phased out md5s purposely?

Patrick

Doug Cutting wrote:
> I have created a candidate build for Avro release 1.3.1.
>
> Changes are listed at:
>
>   http://tinyurl.com/avro131
>
> Please download, test, and vote by 16 March.
>
>   http://people.apache.org/~cutting/avro-1.3.1-rc0/
>
> Thanks,
>
> Doug

Patrick Hunt wrote:
> Have you phased out md5s purposely?

Yes, although perhaps I should not have.  I knew that one was optional,
and that SHA1 is thought to be a better hash than MD5, so assumed that
MD5 was optional.  But now that you've called attention to it, it seems
that SHA1 is optional and MD5 is required (perhaps since tools expect it).

http://www.apache.org/dev/release-signing.html#policy

I have created MD5 hashes for this release candidate & will update
build.sh to create these as well from now on.

Doug

Doug-

It is possible to cut a new release candidate?  I just made two
important commits to trunk for Avro/C that I'd like in 1.3.1.

AVRO-449: CMake-based build system for Avro/C
AVRO-418: avro.h generates errors when included in C++ code

-Matt
On Fri, Mar 12, 2010 at 2:43 PM, Doug Cutting <[EMAIL PROTECTED]> wrote:
> I have created a candidate build for Avro release 1.3.1.
>
> Changes are listed at:
>
>  http://tinyurl.com/avro131
>
> Please download, test, and vote by 16 March.
>
>  http://people.apache.org/~cutting/avro-1.3.1-rc0/
>
> Thanks,
>
> Doug
>

Matt Massie wrote:
> It is possible to cut a new release candidate?  I just made two
> important commits to trunk for Avro/C that I'd like in 1.3.1.
>
> AVRO-449: CMake-based build system for Avro/C
> AVRO-418: avro.h generates errors when included in C++ code

Are you suggesting these should be blockers for 1.3.1?  Are they
regressions?  If so, please mark them as such and -1 this release.
Otherwise they're candidates for 1.3.2 and/or 1.4.0, no?

It does not seem unlikely to me that we'll have reasons for a 1.3.2
release in a few weeks.  Do others think that's too frequent?

Doug

I don't consider them blockers.

If we are planning on releasing regular minor updates, then it can
wait until 1.3.2 in a few weeks.

I'm +1 on this release.

* All tests pass on MacOS and Linux
* md5/sha1 signatures are correct

-Matt

On Tue, Mar 16, 2010 at 10:39 AM, Doug Cutting <[EMAIL PROTECTED]> wrote:
> Matt Massie wrote:
>>
>> It is possible to cut a new release candidate?  I just made two
>> important commits to trunk for Avro/C that I'd like in 1.3.1.
>>
>> AVRO-449: CMake-based build system for Avro/C
>> AVRO-418: avro.h generates errors when included in C++ code
>
> Are you suggesting these should be blockers for 1.3.1?  Are they
> regressions?  If so, please mark them as such and -1 this release. Otherwise
> they're candidates for 1.3.2 and/or 1.4.0, no?
>
> It does not seem unlikely to me that we'll have reasons for a 1.3.2 release
> in a few weeks.  Do others think that's too frequent?
>
> Doug
>

+1

Based on checking checksums and signatures, and running tests.

Tom

On Fri, Mar 12, 2010 at 2:43 PM, Doug Cutting <[EMAIL PROTECTED]> wrote:
> I have created a candidate build for Avro release 1.3.1.
>
> Changes are listed at:
>
>  http://tinyurl.com/avro131
>
> Please download, test, and vote by 16 March.
>
>  http://people.apache.org/~cutting/avro-1.3.1-rc0/
>
> Thanks,
>
> Doug
>

+1 -- full set of tests passed on src archive, md5s pass

Patrick

Doug Cutting wrote:
> I have created a candidate build for Avro release 1.3.1.
>
> Changes are listed at:
>
>   http://tinyurl.com/avro131
>
> Please download, test, and vote by 16 March.
>
>   http://people.apache.org/~cutting/avro-1.3.1-rc0/
>
> Thanks,
>
> Doug