+1 * Set the Maven staging as a repo on my system. * Updated several of my projects that rely heavily on AVRO to use the 1.8.0 version. * Rebuild and ran all the unit tests on those projects; all passed without incident
On Wed, Dec 16, 2015 at 6:55 PM, Tom White <[email protected]> wrote: > I have created a new candidate build for Avro release 1.8.0 following the > rc0 vote in August that didn't pass due to licensing/notice issues. (Thanks > to Ryan and Sean for fixing them!) > > The changes are listed at: > http://s.apache.org/avro180 > > The release artifacts can be found here: > *https://dist.apache.org/repos/dist/dev/avro/avro-1.8.0-rc1/ > <https://dist.apache.org/repos/dist/dev/avro/avro-1.8.0-rc1/>* > > The tag corresponding to this release candidate is > *http://svn.apache.org/repos/asf/avro/tags/release-1.8.0-rc1/ > <http://svn.apache.org/repos/asf/avro/tags/release-1.8.0-rc1/>* > > You can find the KEYS file here: > https://dist.apache.org/repos/dist/release/avro/KEYS > > The Maven staging repository is at: > *https://repository.apache.org/content/repositories/orgapacheavro-1003 > <https://repository.apache.org/content/repositories/orgapacheavro-1003>* > > Please download, verify, and test. This is the first release that has been > built using Docker, so please pay extra attention to the languages you are > interested in. Thanks in advance for voting! > > Cheers, > Tom > -- Best regards / Met vriendelijke groeten, Niels Basjes
