My vote is -1 on rc0 because of the avro-c and documentation issue. I misquoted the contents of the avro-doc-1.3.0.tar.gz file. The correct contents of the file are:
d41d8cd98f00b204e9800998ecf8427e avro-doc-1.3.0.tar.gz so it appears that signature generation is overwriting our docs? Does the C build fail on the build server? Does it have asciidoc and source-highlight installed? % yum install asciidoc source-highlight should fix that problem. -Matt On Tue, Feb 16, 2010 at 9:44 PM, Matt Massie <m...@cloudera.com> wrote: > Also, the avro-doc at > avro-doc-1.3.0.tar.gz<http://people.apache.org/~cutting/avro-1.3.0-RC0/avro-doc-1.3.0.tar.gz> > > Is a 56 byte text file with the following inside... > > " tar.vim version v23b > " Browsing tarfile /private/tmp/avro-doc-1.3.0.tar.gz > " Select a file with cursor and press ENTER > > > gzip: /private/tmp/avro-doc-1.3.0.tar.gz: not in gzip format > > -Matt > > On Tue, Feb 16, 2010 at 9:39 PM, Matt Massie <m...@cloudera.com> wrote: > >> Doug- >> >> I don't see the avro-c artifact at the URL below. >> >> -Matt >> >> >> On Tue, Feb 16, 2010 at 4:07 PM, Doug Cutting <cutt...@apache.org> wrote: >> >>> I have created a candidate build for Avro release 1.3.0. >>> >>> In this release: >>> - the Avro file format has been revised and simplified; >>> - the source tree and release artifacts have been restructured; >>> - the Python port has been largely rewritten; >>> - the C port is now considerably more complete, supporting data files; >>> - a Ruby port has been added, supporting data files and RPC. >>> >>> Please download, test, and vote by 19 February. >>> >>> http://people.apache.org/~cutting/avro-1.3.0-RC0/ >>> >>> Thanks, >>> >>> Doug >>> >> >> >
