The list of currently unresolved issues targeted for 1.5 is at:

http://tinyurl.com/4asjh64

In the interest of ushering 1.5 out the door sooner rather than later,
let's mark things that we should hold the release for as "Blocker".

I propose to remove all non-blockers from this 1.5 list on Monday,
February 21.  Does anyone object?

If you feel strongly that an issue should block the 1.5.0 release and
are willing to work on it to make sure that it can be committed soon,
please change it to blocker.  API changes should be the highest
priority, since the 1.5.0 release will establish API compatibility for
all subsequent 1.5.x bugfix releases.

I already marked a few issues as blockers.

Thanks!

Doug

Hi Doug,
Can AVRO-761 be included in the 1.5.0 release?  The supplied patch fixes
the issue, so hopefully this is just a matter of committing the change.

Best,
Rich
-----Original Message-----
From: Doug Cutting [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 17, 2011 2:35 PM
To: [EMAIL PROTECTED]
Subject: 1.5 release

The list of currently unresolved issues targeted for 1.5 is at:

http://tinyurl.com/4asjh64

In the interest of ushering 1.5 out the door sooner rather than later,
let's mark things that we should hold the release for as "Blocker".

I propose to remove all non-blockers from this 1.5 list on Monday,
February 21.  Does anyone object?

If you feel strongly that an issue should block the 1.5.0 release and
are willing to work on it to make sure that it can be committed soon,
please change it to blocker.  API changes should be the highest
priority, since the 1.5.0 release will establish API compatibility for
all subsequent 1.5.x bugfix releases.

I already marked a few issues as blockers.

Thanks!

Doug

----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.
Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law.
The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses.

References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link:
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.

Java summary of current non-blockers:

  AVRO-738 will close as a result of AVRO-753.
  AVRO-730 will likely make it in.
  AVRO-726 I'll try and get to this, but only after the top 3 blockers are
done.
  
  AVRO-761 Its close, but does not break APIs so is safe for a 1.5.1 if we
run out of time.  We should mark this for 1.5.1 if we can't get to it.  I
marked it with 1.5.0 for now (non-blocker) so its on our radar.

spec related items, these will most likely end up assigned to 1.6.0.

Note, a 1.5.1 release can happen fairly quickly afterwards.  1.5.0 is the
hard one because a couple languages have some significant API changes.
On 2/17/11 11:35 AM, "Doug Cutting" <[EMAIL PROTECTED]> wrote:

>The list of currently unresolved issues targeted for 1.5 is at:
>
>http://tinyurl.com/4asjh64
>
>In the interest of ushering 1.5 out the door sooner rather than later,
>let's mark things that we should hold the release for as "Blocker".
>
>I propose to remove all non-blockers from this 1.5 list on Monday,
>February 21.  Does anyone object?
>
>If you feel strongly that an issue should block the 1.5.0 release and
>are willing to work on it to make sure that it can be committed soon,
>please change it to blocker.  API changes should be the highest
>priority, since the 1.5.0 release will establish API compatibility for
>all subsequent 1.5.x bugfix releases.
>
>I already marked a few issues as blockers.
>
>Thanks!
>
>Doug

> In the interest of ushering 1.5 out the door sooner rather than later,
> let's mark things that we should hold the release for as "Blocker".

I've marked several of the C library issues as blockers, and marked them as targets for 1.5.  They have patches uploaded already, and the existing test cases all pass, so hopefully they just need another pair of eyes to look for glaring errors before they can be committed.

–doug

On 02/18/2011 10:23 AM, Douglas Creager wrote:
> I've marked several of the C library issues as blockers, and marked them as targets for 1.5.  They have patches uploaded already, and the existing test cases all pass, so hopefully they just need another pair of eyes to look for glaring errors before they can be committed.

Great!  Can Bruce, Matt or someone else familiar with the C
implementation please have a look at these?

Thanks,

Doug

I've made 711 a blocker. I'll have it committed this weekend.

Thanks

Thiru

-----Original Message-----
From: Doug Cutting [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 18, 2011 1:05 AM
To: [EMAIL PROTECTED]
Subject: 1.5 release

The list of currently unresolved issues targeted for 1.5 is at:

http://tinyurl.com/4asjh64

In the interest of ushering 1.5 out the door sooner rather than later,
let's mark things that we should hold the release for as "Blocker".

I propose to remove all non-blockers from this 1.5 list on Monday,
February 21.  Does anyone object?

If you feel strongly that an issue should block the 1.5.0 release and
are willing to work on it to make sure that it can be committed soon,
please change it to blocker.  API changes should be the highest
priority, since the 1.5.0 release will establish API compatibility for
all subsequent 1.5.x bugfix releases.

I already marked a few issues as blockers.

Thanks!

Doug

Is it possible to make AVRO-760 (python) a blocker? Unfortunately, I
don't know Python enough to provide a patch. Could someone knows Python
take a look? Thanks!

>From the surface, it looks like a similar problem as Java bug AVRO-702.
The java one has been fixed by Doug. Thanks,

Xiaolu

-----Original Message-----
From: Scott Carey [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 17, 2011 4:38 PM
To: [EMAIL PROTECTED]
Subject: Re: 1.5 release

Java summary of current non-blockers:

  AVRO-738 will close as a result of AVRO-753.
  AVRO-730 will likely make it in.
  AVRO-726 I'll try and get to this, but only after the top 3 blockers
are
done.
  
  AVRO-761 Its close, but does not break APIs so is safe for a 1.5.1 if
we
run out of time.  We should mark this for 1.5.1 if we can't get to it.
I
marked it with 1.5.0 for now (non-blocker) so its on our radar.

spec related items, these will most likely end up assigned to 1.6.0.

Note, a 1.5.1 release can happen fairly quickly afterwards.  1.5.0 is
the
hard one because a couple languages have some significant API changes.
On 2/17/11 11:35 AM, "Doug Cutting" <[EMAIL PROTECTED]> wrote:

>The list of currently unresolved issues targeted for 1.5 is at:
>
>http://tinyurl.com/4asjh64
>
>In the interest of ushering 1.5 out the door sooner rather than later,
>let's mark things that we should hold the release for as "Blocker".
>
>I propose to remove all non-blockers from this 1.5 list on Monday,
>February 21.  Does anyone object?
>
>If you feel strongly that an issue should block the 1.5.0 release and
>are willing to work on it to make sure that it can be committed soon,
>please change it to blocker.  API changes should be the highest
>priority, since the 1.5.0 release will establish API compatibility for
>all subsequent 1.5.x bugfix releases.
>
>I already marked a few issues as blockers.
>
>Thanks!
>
>Doug

----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.
Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law.
The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses.

References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link:
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.

On 02/17/2011 11:35 AM, Doug Cutting wrote:
> The list of currently unresolved issues targeted for 1.5 is at:
>
> http://tinyurl.com/4asjh64
>
> In the interest of ushering 1.5 out the door sooner rather than later,
> let's mark things that we should hold the release for as "Blocker".
>
> I propose to remove all non-blockers from this 1.5 list on Monday,
> February 21.  Does anyone object?

I will change all the remaining 1.5.0 blockers to 1.5.1.  If any of
these are committed before we release 1.5.0 then they can move back to
1.5.0, but we won't hold 1.5.0 for these non-blockers.  Okay?

Doug

I know I'm a bit late, hopefully not too late.

> If you feel strongly that an issue should block the 1.5.0 release and
> are willing to work on it to make sure that it can be committed soon,
> please change it to blocker.

I opened AVRO-774[1] yesterday mainly to fix the JBoss repository
definition in the Java Maven build. It is an easy fix and has a patch
attached but me not being a committer I didn't want to set it to
blocker. I'd love to see it included though.

Cheers,
Lars

[1] <https://issues.apache.org/jira/browse/AVRO-774>

On 02/23/2011 05:24 AM, Lars Francke wrote:
> I opened AVRO-774[1] yesterday mainly to fix the JBoss repository
> definition in the Java Maven build. It is an easy fix and has a patch
> attached but me not being a committer I didn't want to set it to
> blocker. I'd love to see it included though.

I think we can get this in to 1.5.0.  I'm marking issues for 1.5.1 which
shouldn't block 1.5.0, but, if they're committed before 1.5.0 is rolled
then they'll be included in 1.5.0, if that makes sense.

Doug

On 02/17/2011 11:35 AM, Doug Cutting wrote:
> The list of currently unresolved issues targeted for 1.5 is at:
>
> http://tinyurl.com/4asjh64

We're down to 5 blockers, assigned to either Scott or Douglas.  It'd be
great if we can get these all either committed or postponed to 1.5.1
soon so that we can roll the first 1.5.0 release candidate.

Doug

> We're down to 5 blockers, assigned to either Scott or Douglas.  It'd be
> great if we can get these all either committed or postponed to 1.5.1
> soon so that we can roll the first 1.5.0 release candidate.

I haven't heard any objections to the patches on the issues that are mine, and all of the tests pass.  Unless I hear otherwise, I'll commit them in the morning.

cheers
–doug

I'll submit an updated patch on my remaining ticket tomorrow.

On 2/24/11 4:04 PM, "Doug Cutting" <[EMAIL PROTECTED]> wrote:

>On 02/17/2011 11:35 AM, Doug Cutting wrote:
>> The list of currently unresolved issues targeted for 1.5 is at:
>>
>> http://tinyurl.com/4asjh64
>
>We're down to 5 blockers, assigned to either Scott or Douglas.  It'd be
>great if we can get these all either committed or postponed to 1.5.1
>soon so that we can roll the first 1.5.0 release candidate.
>
>Doug