No,
This has been closed.
The vote has failed!

S

On Mon, May 1, 2017 at 6:08 PM, Harsha Chintalapani <a...@harsha.io> wrote:

> Hi,
>      is this VOTE thread still active.
> Thanks,
> Harsha
>
> On Thu, Apr 13, 2017 at 11:13 AM Sean Busbey <bus...@cloudera.com> wrote:
>
> > Thanks for continuing to push on this Suraj!
> >
> > On Thu, Apr 13, 2017 at 9:03 AM, suraj acharya <suraj....@gmail.com>
> > wrote:
> > > Hi Gabor,
> > >
> > > Thanks for looking at the RC.
> > >
> > > * The issue of the missing file seems like a bad push or some other
> > issue.
> > > * Regarding the JS issue, no it was not an intentional numbering. The
> > > release guide didnt have a mention of it and I missed it.
> > > For everyone, this is the value that needs to be bumped.
> > > https://github.com/apache/avro/blob/branch-1.8/lang/js/package.json#L3
> > >
> > > I dont believe this RC can pass and I *close* the vote.
> > >
> > > I will try again to build a new RC may be next month since all pushes
> on
> > > 1.8 were stopped while I was working on this.
> > >
> > > Once again thanks for taking the time
> > >
> > > Suraj Acharya
> > >
> > > -Suraj Acharya
> > >
> > > On Thu, Apr 13, 2017 at 6:59 AM, Gabor Szadovszky <
> > > gabor.szadovs...@cloudera.com> wrote:
> > >
> > >> Hi Suraj,
> > >>
> > >> Thanks a lot for taking care of this new release.
> > >>
> > >> Verified the checksums and ASC under https://dist.apache.org/repos/
> > >> dist/dev/avro/avro-1.8.2-rc3/ <https://dist.apache.org/
> > >> repos/dist/dev/avro/avro-1.8.2-rc3/>
> > >> Is it intentional that the JS has the version 1.8.0 while all the
> others
> > >> have 1.8.2?
> > >> All the checksums and ASC are correct.
> > >>
> > >> By unpacking the src tar I’ve got an unclear error message:
> > >> tar: copyfile unpack (avro-src-1.8.2/lang/java/
> > >> mapred/src/test/resources/org/apache/avro/mapreduce/
> > >> mapreduce-test-input.avro/SUCCESS.crc) failed: No such file or
> directory
> > >> In addition this file does not exist in the github repo under the
> label
> > >> release-1.8.2-rc3. I guess because of this anomaly I was not able to
> do
> > a
> > >> mvn clean install in the unpacked src archive (unit test failure).
> > >> Apart from that the src archive contains the same files as in the
> repo.
> > >>
> > >> mvn clean install works properly with the related tag in the github
> > repo.
> > >>
> > >> Regards,
> > >> Gabor
> > >>
> > >>
> > >> > On 12 Apr 2017, at 20:35, Suraj Acharya <su...@apache.org> wrote:
> > >> >
> > >> > Hi everyone,
> > >> >
> > >> > I propose the following RC to be released as official Apache Avro
> > 1.8.2
> > >> > release.
> > >> >
> > >> > The commit id is e38f7074d7c8f9156b39c8310302486ced93767a
> > >> >
> > >> > * This corresponds to the tag: release-1.8.2-rc3
> > >> > * https://s.apache.org/avro-1.8.2-rc3
> > >> >
> > >> > The release tarball, signature, and checksums are here:
> > >> > * https://dist.apache.org/repos/dist/dev/avro/avro-1.8.2-rc3/
> > >> >
> > >> > You can find the KEYS file here:
> > >> > * https://dist.apache.org/repos/dist/release/avro/KEYS
> > >> >
> > >> > Binary artifacts for Java are staged in Nexus here:
> > >> > *
> > https://repository.apache.org/content/repositories/orgapacheavro-1012/
> > >> >
> > >> > This release includes:
> > >> > * A spec for single-message Avro encoding and a Java implementation
> > >> > * Java: Bug fixes for Java logical types
> > >> > * Java: Support for Decimal with specific classes
> > >> > * Ruby: A fix for compatibility when using snappy
> > >> > * Python 3: Updated to use the standard module-level logging pattern
> > >> > * C++: Support for Boost >= 1.59
> > >> > * And more bug fixes...
> > >> >
> > >> > Please download, verify, and test. This vote will remain open for at
> > >> least
> > >> > 72 hours. Given sufficient votes, I would like to close it on or
> about
> > >> 9AM
> > >> > CDT on Wednesday, 19 April 2017.
> > >> >
> > >> > [ ] +1 Release this as Apache Avro 1.8.2
> > >> > [ ] +0
> > >> > [ ] -1 Do not release this because...
> > >> >
> > >> > --
> > >> > Suraj Acharya
> > >>
> > >>
> >
> >
> >
> > --
> > busbey
> >
>

Reply via email to