avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Cutting <cutt...@apache.org>
Subject Re: release 1.7.7 soon?
Date Thu, 03 Jul 2014 21:15:21 GMT
I just tried but am currently unable to get the C++ to compile.  It
fails for me with:

lang/c++/api/GenericDatum.hh:474:16: error: request for member
‘resize’ in ‘((avro::GenericFixed*)this)->avro::GenericFixed::value_’,
which is of non-class type ‘int’

Does anyone have any idea what the problem here is?

Please commit AVRO-1448.

Doug

On Thu, Jul 3, 2014 at 2:10 PM, Christophe Taton <taton@wibidata.com> wrote:
> Hey Doug,
>
> When will you start the release this afternoon?
> Do I have time to push AVRO-1448?
>
> Thanks,
> C.
>
>
> On Thu, Jul 3, 2014 at 1:36 PM, Doug Cutting <cutting@apache.org> wrote:
>
>> I intend to create a 1.7.7 release candidate today and call a vote.
>> There may be patches out there that are nearly ready and should
>> perhaps be included in 1.7.7, but I'll be gone next week and, even if
>> this vote doesn't pass, the process of creating the candidate and
>> calling the vote should at least get us closer to the release.
>>
>> Doug
>>
>> On Fri, May 23, 2014 at 3:05 PM, Doug Cutting <cutting@apache.org> wrote:
>> > There've been some requests to release Avro version 1.7.7 soon.
>> >
>> > I'm happy to create a release candidate next week and call a vote.
>> >
>> > I suspect there are a number of issues we might commit first.
>> >
>> > The list of open issues set to be fixed in 1.7.7 is here:
>> >
>> >   http://s.apache.org/avro177unresolved
>> >
>> > If there are issues you'd like to get into 1.7.7, these should be
>> > marked as "Fix for: 1.7.7" and as "Patch Available".  These each then
>> > need be reviewed and a decision whether to include them in the
>> > release.
>> >
>> > Can folks please review "Patch Available" issues and indicate whether
>> > they think it should be committed?  A committer must make the final
>> > decision of whether to commit each change, but reviews by independent
>> > non-committers help considerably.
>> >
>> > API changes in 1.7.7 must be back-compatible, and data format changes
>> > must be both back- and forward-compatible.
>> >
>> > Thanks,
>> >
>> > Doug
>>

Mime
View raw message