I'd like to roll a 1.7.0 candidate release soon.

The current list of unresolved issues for 1.7.0 is at:

   http://s.apache.org/avro170

I'll be going through this, committing things that are ready or that I
can make ready, and pushing the remainder to 1.7.1 or 1.8.0.

Are there issues that you'd like to get into 1.7.0 that are not in that
list?

Doug

Doug,

There are a handful of minor bugs in C++ code generation. I'd like to fix them. I should be able to do in a couple of days.
Thanks

Thiru

________________________________
 From: Doug Cutting <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Saturday, 12 May 2012 5:20 AM
Subject: 1.7.0 release soon?
 
I'd like to roll a 1.7.0 candidate release soon.

The current list of unresolved issues for 1.7.0 is at:

  http://s.apache.org/avro170

I'll be going through this, committing things that are ready or that I can make ready, and pushing the remainder to 1.7.1 or 1.8.0.

Are there issues that you'd like to get into 1.7.0 that are not in that list?

Doug

Hi Doug,

Any chance we could check in the test case for https://issues.apache.org/jira/browse/AVRO-1058 ? This would be useful even if the issue can't be released soon. The issues are still present, including with Thiru's latest fixes.

Wolfgang.

On May 11, 2012, at 4:50 PM, Doug Cutting wrote:

> I'd like to roll a 1.7.0 candidate release soon.
>
> The current list of unresolved issues for 1.7.0 is at:
>
>  http://s.apache.org/avro170
>
> I'll be going through this, committing things that are ready or that I can make ready, and pushing the remainder to 1.7.1 or 1.8.0.
>
> Are there issues that you'd like to get into 1.7.0 that are not in that list?
>
> Doug

There have just been a number of critical bugs reported against avro-c.

I am on holiday until Monday evening but can look at the submitted patches after that.

 - Bruce

Sent from my iPhone

On May 12, 2012, at 6:50 AM, Doug Cutting <[EMAIL PROTECTED]> wrote:

> I'd like to roll a 1.7.0 candidate release soon.
>
> The current list of unresolved issues for 1.7.0 is at:
>
>  http://s.apache.org/avro170
>
> I'll be going through this, committing things that are ready or that I can make ready, and pushing the remainder to 1.7.1 or 1.8.0.
>
> Are there issues that you'd like to get into 1.7.0 that are not in that list?
>
> Doug

> There have just been a number of critical bugs reported against avro-c.
>
> I am on holiday until Monday evening but can look at the submitted patches after that.

Same for me — I'm away this weekend but can look at the patches on Monday, too.

It would be great if a python developer could review my patch for AVRO-283. If it could get committed I could finish resolving AVRO-973, which has been preventing us from using python with some of our schemas.  

I'd love to get them taken care of in 1.7 if possible.

On May 11, 2012, at 7:50 PM, Doug Cutting <[EMAIL PROTECTED]> wrote:

> I'd like to roll a 1.7.0 candidate release soon.
>
> The current list of unresolved issues for 1.7.0 is at:
>
>  http://s.apache.org/avro170
>
> I'll be going through this, committing things that are ready or that I can make ready, and pushing the remainder to 1.7.1 or 1.8.0.
>
> Are there issues that you'd like to get into 1.7.0 that are not in that list?
>
> Doug

> It would be great if a python developer could review my patch for AVRO-283. If it could get committed I could finish resolving AVRO-973, which has been preventing us from using python with some of our schemas.
>
> I'd love to get them taken care of in 1.7 if possible.
Sorry for the late reply, I'll do my best to have a look today/tomorrow.

Okay, I've committed the stuff that looks ready to me.

Are there still things that others want to get into this release
before I create a candidate?

Note that there will probably be a 1.7.1 release not too long after,
so we shouldn't hold this up for compatible changes unless they're
fixing critical bugs.

Doug

On Fri, May 11, 2012 at 4:50 PM, Doug Cutting <[EMAIL PROTECTED]> wrote:
> I'd like to roll a 1.7.0 candidate release soon.
>
> The current list of unresolved issues for 1.7.0 is at:
>
>  http://s.apache.org/avro170
>
> I'll be going through this, committing things that are ready or that I can
> make ready, and pushing the remainder to 1.7.1 or 1.8.0.
>
> Are there issues that you'd like to get into 1.7.0 that are not in that
> list?
>
> Doug

> Okay, I've committed the stuff that looks ready to me.
>
> Are there still things that others want to get into this release
> before I create a candidate?
>
> Note that there will probably be a 1.7.1 release not too long after,
> so we shouldn't hold this up for compatible changes unless they're
> fixing critical bugs.

I just tested all of the available patches for the C library on my Windows box.  Apologies for the delay, I didn't have access to this machine until today.  They look good; I'm going to merge them into SVN now so they're in for 1.7.0.

–doug

On Sun, May 20, 2012 at 8:38 PM, Douglas Creager <[EMAIL PROTECTED]>wrote:

> > Okay, I've committed the stuff that looks ready to me.
> >
> > Are there still things that others want to get into this release
> > before I create a candidate?
> >
> > Note that there will probably be a 1.7.1 release not too long after,
> > so we shouldn't hold this up for compatible changes unless they're
> > fixing critical bugs.
>
> I just tested all of the available patches for the C library on my Windows
> box.  Apologies for the delay, I didn't have access to this machine until
> today.  They look good; I'm going to merge them into SVN now so they're in
> for 1.7.0.
>

They looked good to me as well ... but I was in the same position without
access to the right machine.

 - Bruce

> I just tested all of the available patches for the C library on my Windows box.  Apologies for the delay, I didn't have access to this machine until today.  They look good; I'm going to merge them into SVN now so they're in for 1.7.0.

C library should be good to go.  All of the recent patches have been applied.  AVRO-1089 is still open, but it won't require any API changes, and will require some more investigation.  So it can wait for 1.7.1.

–doug

On Sun, May 20, 2012 at 6:31 PM, Douglas Creager <[EMAIL PROTECTED]>wrote:

> > I just tested all of the available patches for the C library on my
> Windows box.  Apologies for the delay, I didn't have access to this machine
> until today.  They look good; I'm going to merge them into SVN now so
> they're in for 1.7.0.
>
> C library should be good to go.  All of the recent patches have been
> applied.  AVRO-1089 is still open, but it won't require any API changes,
> and will require some more investigation.  So it can wait for 1.7.1.
>
> –doug
>
>
Hello!
Guys, what about https://issues.apache.org/jira/browse/AVRO-1087 ?

C++ is good to go as well.I tried to assign AVRO-1026 and AVRO-1066 to their respective reporters. JIRA wouldn't accept their names as assignees. Can someone help?

Of the three problems reported in AVRO-1058 is the first one is a real bug. I created a separate JIRA AVRO-1097 and submitted a patch. Doug can you review and check it in before the release? Thanks.

Thiru

________________________________
 From: Douglas Creager <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Sunday, 20 May 2012 8:01 PM
Subject: Re: 1.7.0 release soon?
 
> I just tested all of the available patches for the C library on my Windows box.  Apologies for the delay, I didn't have access to this machine until today.  They
 look good; I'm going to merge them into SVN now so they're in for 1.7.0.

C library should be good to go.  All of the recent patches have been applied.  AVRO-1089 is still open, but it won't require any API changes, and will require some more investigation.  So it can wait for 1.7.1.

–doug

On 05/21/2012 01:17 AM, Thiruvalluvan MG wrote:
> C++ is good to go as well.

Great!

> I tried to assign AVRO-1026 and AVRO-1066 to their respective
> reporters. JIRA wouldn't accept their names as assignees. Can someone
> help?

 From https://issues.apache.org/jira/browse/AVRO, hit the "Administer
Project" link.  Then, under "People", click "View Project Roles".
Committers can then add new folks to the Contributor role on that page.

I just added the authors of the patches for these two issues and
assigned them.

> Of the three problems reported in AVRO-1058 is the first one is a
> real bug. I created a separate JIRA AVRO-1097 and submitted a patch.
> Doug can you review and check it in before the release? Thanks.

I added some comments there.  Do you think this is critical?  To my
thinking it only affects which exception is thrown when trying to read
invalid input.  Or did I miss something?

Thiru, can you please have a look at AVRO-1098?  Without this I cannot
build the release candidate.

Thanks,

Doug

I`ve got one more crash bug in avro-c. Working on patch right now.

On Tue, May 22, 2012 at 3:18 AM, Doug Cutting <[EMAIL PROTECTED]> wrote:

> On 05/21/2012 01:17 AM, Thiruvalluvan MG wrote:
>
>> C++ is good to go as well.
>>
>
> Great!
>
>
>  I tried to assign AVRO-1026 and AVRO-1066 to their respective
>> reporters. JIRA wouldn't accept their names as assignees. Can someone
>> help?
>>
>
> From https://issues.apache.org/**jira/browse/AVRO<https://issues.apache.org/jira/browse/AVRO>,
> hit the "Administer Project" link.  Then, under "People", click "View
> Project Roles". Committers can then add new folks to the Contributor role
> on that page.
>
> I just added the authors of the patches for these two issues and assigned
> them.
>
>
>  Of the three problems reported in AVRO-1058 is the first one is a
>> real bug. I created a separate JIRA AVRO-1097 and submitted a patch.
>> Doug can you review and check it in before the release? Thanks.
>>
>
> I added some comments there.  Do you think this is critical?  To my
> thinking it only affects which exception is thrown when trying to read
> invalid input.  Or did I miss something?
>
> Thiru, can you please have a look at AVRO-1098?  Without this I cannot
> build the release candidate.
>
> Thanks,
>
> Doug
>
>
>