I have created a candidate build for Avro release 1.7.0.

Changes are listed at:

   http://s.apache.org/avro170notes

Please download the sources, check them, and vote.

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

The Maven staging repository is at:

   https://repository.apache.org/content/repositories/orgapacheavro-124/

Thanks in advance for voting!

Doug

+1 Checksums are correct, tests pass, licensing looks good.

I'd like to get this out soon so that folks can start depending on the
1.7 series.  If there are bugs we can address them rapidly in a 1.7.1
release.  So we should really only hold this for a fix or improvement
that introduces an incompatibility.

Doug

On 05/23/2012 03:06 PM, Doug Cutting wrote:
> I have created a candidate build for Avro release 1.7.0.
>
> Changes are listed at:
>
> http://s.apache.org/avro170notes
>
> Please download the sources, check them, and vote.
>
> http://people.apache.org/~cutting/avro-1.7.0-rc0/
>
> The Maven staging repository is at:
>
> https://repository.apache.org/content/repositories/orgapacheavro-124/
>
> Thanks in advance for voting!
>
> Doug

Doug, can you please review these patches:
https://issues.apache.org/jira/browse/AVRO-1101
https://issues.apache.org/jira/browse/AVRO-1102

This is a bug fixes (one of them are critical), so I think it`s better to
include it in 1.7.0 release.
Thanks!

On Wed, Jun 6, 2012 at 9:09 PM, Doug Cutting <[EMAIL PROTECTED]> wrote:

> +1 Checksums are correct, tests pass, licensing looks good.
>
> I'd like to get this out soon so that folks can start depending on the 1.7
> series.  If there are bugs we can address them rapidly in a 1.7.1 release.
>  So we should really only hold this for a fix or improvement that
> introduces an incompatibility.
>
> Doug
>
>
> On 05/23/2012 03:06 PM, Doug Cutting wrote:
>
>> I have created a candidate build for Avro release 1.7.0.
>>
>> Changes are listed at:
>>
>> http://s.apache.org/**avro170notes <http://s.apache.org/avro170notes>
>>
>> Please download the sources, check them, and vote.
>>
>> http://people.apache.org/~**cutting/avro-1.7.0-rc0/<http://people.apache.org/%7Ecutting/avro-1.7.0-rc0/>
>>
>> The Maven staging repository is at:
>>
>> https://repository.apache.org/**content/repositories/**orgapacheavro-124/<https://repository.apache.org/content/repositories/orgapacheavro-124/>
>>
>> Thanks in advance for voting!
>>
>> Doug
>>
>

Maxim,

I'm not very familiar with the Avro C code.  I hope that someone who
is will review your patches soon as they look to fix critical bugs
there.

I agree it would be best to get these included an in a release as soon
as possible.  Once they're committed I'd be happy to create a new
release candidate and call a vote on it.  Whether this is 1.7.0 or
1.7.1 doesn't make much difference.  With 2 more +1 votes from PMC
members we could have 1.7.0 released today.

Doug

On Wed, Jun 6, 2012 at 11:40 PM, Maxim Pugachev <[EMAIL PROTECTED]> wrote:
> Doug, can you please review these patches:
> https://issues.apache.org/jira/browse/AVRO-1101
> https://issues.apache.org/jira/browse/AVRO-1102
>
> This is a bug fixes (one of them are critical), so I think it`s better to
> include it in 1.7.0 release.
> Thanks!
>
> On Wed, Jun 6, 2012 at 9:09 PM, Doug Cutting <[EMAIL PROTECTED]> wrote:
>
>> +1 Checksums are correct, tests pass, licensing looks good.
>>
>> I'd like to get this out soon so that folks can start depending on the 1.7
>> series.  If there are bugs we can address them rapidly in a 1.7.1 release.
>>  So we should really only hold this for a fix or improvement that
>> introduces an incompatibility.
>>
>> Doug
>>
>>
>> On 05/23/2012 03:06 PM, Doug Cutting wrote:
>>
>>> I have created a candidate build for Avro release 1.7.0.
>>>
>>> Changes are listed at:
>>>
>>> http://s.apache.org/**avro170notes <http://s.apache.org/avro170notes>
>>>
>>> Please download the sources, check them, and vote.
>>>
>>> http://people.apache.org/~**cutting/avro-1.7.0-rc0/<http://people.apache.org/%7Ecutting/avro-1.7.0-rc0/>
>>>
>>> The Maven staging repository is at:
>>>
>>> https://repository.apache.org/**content/repositories/**orgapacheavro-124/<https://repository.apache.org/content/repositories/orgapacheavro-124/>
>>>
>>> Thanks in advance for voting!
>>>
>>> Doug
>>>
>>

> I'm not very familiar with the Avro C code.  I hope that someone who
> is will review your patches soon as they look to fix critical bugs
> there.
>
> I agree it would be best to get these included an in a release as soon
> as possible.  Once they're committed I'd be happy to create a new
> release candidate and call a vote on it.  Whether this is 1.7.0 or
> 1.7.1 doesn't make much difference.  With 2 more +1 votes from PMC
> members we could have 1.7.0 released today.

I can take care of this right now.  Sorry about the delay, I got drawn onto a couple of other projects at work over the past couple of weeks.

[also] Doug

> I can take care of this right now.  Sorry about the delay, I got drawn onto a couple of other projects at work over the past couple of weeks.

I just committed the patch in AVRO-1102 to trunk.  Doug, is that enough to let you cut a new 1.7.0 release candidate including the patch?  Or do I need to merge that commit into another branch first?

For AVRO-1101, I just posted a comment on the issue — I'm not sure if the patch you've uploaded is the right way to solve the problem.  So for this one, I think we can wait to address it in 1.7.1.  That will give us time to work out the right solution.  There are more details in my comment on the issue, but I think it needs a documentation update, and not a code update.

–doug

On Thu, Jun 7, 2012 at 10:54 AM, Douglas Creager <[EMAIL PROTECTED]>wrote:

> I just committed the patch in AVRO-1102 to trunk.  Doug, is that enough to
> let you cut a new 1.7.0 release candidate including the patch?
>

That's enough.  I can roll another candidate and hope folks vote promptly.
 There are folks who need a 1.7 release ASAP.

Doug

A new release candidate introduces at least a 1 week delay for the vote.
If we can get two other PMC members to approve this release, 1.7.0 can go
out and we can create a 1.7.1 immediately after.

Unfortunately I will not have time to test either of these until next
Monday.

-Scott

On 6/7/12 10:54 AM, "Douglas Creager" <[EMAIL PROTECTED]> wrote:

>> I can take care of this right now.  Sorry about the delay, I got drawn
>>onto a couple of other projects at work over the past couple of weeks.
>
>I just committed the patch in AVRO-1102 to trunk.  Doug, is that enough
>to let you cut a new 1.7.0 release candidate including the patch?  Or do
>I need to merge that commit into another branch first?
>
>For AVRO-1101, I just posted a comment on the issue ‹ I'm not sure if the
>patch you've uploaded is the right way to solve the problem.  So for this
>one, I think we can wait to address it in 1.7.1.  That will give us time
>to work out the right solution.  There are more details in my comment on
>the issue, but I think it needs a documentation update, and not a code
>update.
>
>­doug
>