I'd like to try to release 1.6.0 soon, perhaps making a release
candidate next week.  Are there particular issues that folks would like
to get into 1.6.0 that are not yet committed?  I hope include AVRO-803.

Doug

Doug,

I'd like to clear a few backlog items in Java C++. I'll complete them in a
couple of days.

Thanks

Thiru

-----Original Message-----
From: Doug Cutting [mailto:[EMAIL PROTECTED]]
Sent: Saturday, October 08, 2011 2:42 AM
To: [EMAIL PROTECTED]
Subject: release 1.6.0 soon?

I'd like to try to release 1.6.0 soon, perhaps making a release
candidate next week.  Are there particular issues that folks would like
to get into 1.6.0 that are not yet committed?  I hope include AVRO-803.

Doug

> I'd like to clear a few backlog items in Java C++. I'll complete them in a
> couple of days.

Ditto for the C library.  I'd like to make sure I have a stable version of the new value API committed in time for 1.6.0.  I'll make sure that's done over the weekend.

cheers
–doug

Specifically, I want to address the following JIRA tickets in the next few
days.

https://issues.apache.org/jira/browse/AVRO-918
https://issues.apache.org/jira/browse/AVRO-917
https://issues.apache.org/jira/browse/AVRO-916
https://issues.apache.org/jira/browse/AVRO-915
https://issues.apache.org/jira/browse/AVRO-913
https://issues.apache.org/jira/browse/AVRO-908
https://issues.apache.org/jira/browse/AVRO-869
https://issues.apache.org/jira/browse/AVRO-840

Thanks

Thiru

-----Original Message-----
From: Thiruvalluvan M G [mailto:[EMAIL PROTECTED]]
Sent: Saturday, October 08, 2011 10:09 AM
To: '[EMAIL PROTECTED]'
Subject: RE: release 1.6.0 soon?

Doug,

I'd like to clear a few backlog items in Java C++. I'll complete them in a
couple of days.

Thanks

Thiru

-----Original Message-----
From: Doug Cutting [mailto:[EMAIL PROTECTED]]
Sent: Saturday, October 08, 2011 2:42 AM
To: [EMAIL PROTECTED]
Subject: release 1.6.0 soon?

I'd like to try to release 1.6.0 soon, perhaps making a release
candidate next week.  Are there particular issues that folks would like
to get into 1.6.0 that are not yet committed?  I hope include AVRO-803.

Doug

> Ditto for the C library.  I'd like to make sure I have a stable version of the new value API committed in time for 1.6.0.  I'll make sure that's done over the weekend.

I just opened up JIRA issues for a couple of patches I had queued up on my github branch.  I'll commit them to SVN in the next day or two, unless I hear objections about any of them.

cheers
–doug

> I just opened up JIRA issues for a couple of patches I had queued up on my github branch.  I'll commit them to SVN in the next day or two, unless I hear objections about any of them.

I've checked in all of the changes that I wanted to include in 1.6.0.  Vivek Nadkarni has reported another one that I should probably fix for 1.6.0, but he's included a patch, so that shouldn't take long.

The one issue left to discuss is AVRO-467.  It moves the build system for the C library over from autotools to CMake.  I've been using the CMake scripts myself for quite awhile, and they seem pretty stable.  The patch on AVRO-467 removes the autotools files, and updates the build.sh script (used by the multi-language driver script) to use CMake instead of autotools.  If anyone has the time, can you verify that build.sh works with the patch applied?  If so, we can start using CMake from 1.6.0 onwards.

The build.sh script is set up to build the C library documentation and include it in the source tarball.  The build servers would need to have asciidoc [1] and source-highlight [2] installed for this to work.

[1] http://www.methods.co.nz/asciidoc
[2] http://www.gnu.org/software/src-highlite/

cheers
–doug

My C++ changes are also almost done. From my original list, only the
documentation JIRA is still open. I'll close it tomorrow. While documenting
I discovered two minor problems. I'll also have them addressed tomorrow.

Thanks

Thiru

-----Original Message-----
From: Douglas Creager [mailto:[EMAIL PROTECTED]]
Sent: Saturday, October 15, 2011 8:36 PM
To: [EMAIL PROTECTED]
Subject: Re: release 1.6.0 soon?

> I just opened up JIRA issues for a couple of patches I had queued up on my
github branch.  I'll commit them to SVN in the next day or two, unless I
hear objections about any of them.

I've checked in all of the changes that I wanted to include in 1.6.0.  Vivek
Nadkarni has reported another one that I should probably fix for 1.6.0, but
he's included a patch, so that shouldn't take long.

The one issue left to discuss is AVRO-467.  It moves the build system for
the C library over from autotools to CMake.  I've been using the CMake
scripts myself for quite awhile, and they seem pretty stable.  The patch on
AVRO-467 removes the autotools files, and updates the build.sh script (used
by the multi-language driver script) to use CMake instead of autotools.  If
anyone has the time, can you verify that build.sh works with the patch
applied?  If so, we can start using CMake from 1.6.0 onwards.

The build.sh script is set up to build the C library documentation and
include it in the source tarball.  The build servers would need to have
asciidoc [1] and source-highlight [2] installed for this to work.

[1] http://www.methods.co.nz/asciidoc
[2] http://www.gnu.org/software/src-highlite/

cheers
-doug

We should consider updating our dependencies where appropriate.

* We can use a newer Apache parent project version.

Maven versions report:
[INFO] The following dependencies in Dependency Management have newer
versions:
[INFO]   net.sf.jopt-simple:jopt-simple ...................... 3.2 ->
4.0-beta1
[INFO]   org.apache.hadoop:hadoop-core ................... 0.20.2 ->
0.20.204.0
[INFO]   org.codehaus.jackson:jackson-mapper-asl ............... 1.7.3 ->
1.9.0
[INFO]   org.jboss.netty:netty ..................... 3.2.4.Final ->
3.2.5.Final
[INFO]   org.xerial.snappy:snappy-java ..................... 1.0.3.2 ->
1.0.4.1
[INFO] The following dependencies in Dependencies have newer versions:
[INFO]   junit:junit ............................................ 4.8.2 ->
4.10
[INFO]   org.slf4j:slf4j-api ................................... 1.6.1 ->
1.6.2
[INFO]   org.slf4j:slf4j-simple ................................ 1.6.1 ->
1.6.2
[INFO]   org.apache.maven:maven-plugin-api .................... 2.0.10 ->
3.0.3
[INFO]   org.apache.maven:maven-project ................. 2.0.10 ->
3.0-alpha-2
[INFO]   org.apache.ant:ant .................................... 1.7.1 ->
1.8.2
[INFO]   org.apache.velocity:velocity ...................... 1.6.4 ->
1.7-beta1
[INFO] The following plugin updates are available:
[INFO]   org.codehaus.mojo:exec-maven-plugin .................... 1.2 ->
1.2.1
[INFO]   maven-surefire-plugin ................................... 2.6 ->
2.10
[INFO]   maven-plugin-plugin ...................................... 2.7 ->
2.9
[INFO]   maven-jar-plugin ..................................... 2.3.1 ->
2.3.2
[INFO] maven-antrun-plugin ...................................... 1.3 ->
1.6

On 10/7/11 2:11 PM, "Doug Cutting" <[EMAIL PROTECTED]> wrote:

>I'd like to try to release 1.6.0 soon, perhaps making a release
>candidate next week.  Are there particular issues that folks would like
>to get into 1.6.0 that are not yet committed?  I hope include AVRO-803.
>
>Doug

Hi all,

I'm done with all the changes I wanted in.

Thanks

Thiru

-----Original Message-----
From: Thiruvalluvan M G [mailto:[EMAIL PROTECTED]]
Sent: Sunday, October 16, 2011 1:09 AM
To: '[EMAIL PROTECTED]'
Subject: RE: release 1.6.0 soon?

My C++ changes are also almost done. From my original list, only the
documentation JIRA is still open. I'll close it tomorrow. While documenting
I discovered two minor problems. I'll also have them addressed tomorrow.

Thanks

Thiru

-----Original Message-----
From: Douglas Creager [mailto:[EMAIL PROTECTED]]
Sent: Saturday, October 15, 2011 8:36 PM
To: [EMAIL PROTECTED]
Subject: Re: release 1.6.0 soon?

> I just opened up JIRA issues for a couple of patches I had queued up on my
github branch.  I'll commit them to SVN in the next day or two, unless I
hear objections about any of them.

I've checked in all of the changes that I wanted to include in 1.6.0.  Vivek
Nadkarni has reported another one that I should probably fix for 1.6.0, but
he's included a patch, so that shouldn't take long.

The one issue left to discuss is AVRO-467.  It moves the build system for
the C library over from autotools to CMake.  I've been using the CMake
scripts myself for quite awhile, and they seem pretty stable.  The patch on
AVRO-467 removes the autotools files, and updates the build.sh script (used
by the multi-language driver script) to use CMake instead of autotools.  If
anyone has the time, can you verify that build.sh works with the patch
applied?  If so, we can start using CMake from 1.6.0 onwards.

The build.sh script is set up to build the C library documentation and
include it in the source tarball.  The build servers would need to have
asciidoc [1] and source-highlight [2] installed for this to work.

[1] http://www.methods.co.nz/asciidoc
[2] http://www.gnu.org/software/src-highlite/

cheers
-doug

Scott,

This sounds like a good idea.

Do you want to file an issue and patch for this or should I?

Doug

On 10/15/2011 07:21 PM, Scott Carey wrote:
> We should consider updating our dependencies where appropriate.
>
> * We can use a newer Apache parent project version.
>
> Maven versions report:
> [INFO] The following dependencies in Dependency Management have newer
> versions:
> [INFO]   net.sf.jopt-simple:jopt-simple ...................... 3.2 ->
> 4.0-beta1
> [INFO]   org.apache.hadoop:hadoop-core ................... 0.20.2 ->
> 0.20.204.0
> [INFO]   org.codehaus.jackson:jackson-mapper-asl ............... 1.7.3 ->
> 1.9.0
> [INFO]   org.jboss.netty:netty ..................... 3.2.4.Final ->
> 3.2.5.Final
> [INFO]   org.xerial.snappy:snappy-java ..................... 1.0.3.2 ->
> 1.0.4.1
>
>
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO]   junit:junit ............................................ 4.8.2 ->
> 4.10
> [INFO]   org.slf4j:slf4j-api ................................... 1.6.1 ->
> 1.6.2
> [INFO]   org.slf4j:slf4j-simple ................................ 1.6.1 ->
> 1.6.2
> [INFO]   org.apache.maven:maven-plugin-api .................... 2.0.10 ->
> 3.0.3
> [INFO]   org.apache.maven:maven-project ................. 2.0.10 ->
> 3.0-alpha-2
> [INFO]   org.apache.ant:ant .................................... 1.7.1 ->
> 1.8.2
> [INFO]   org.apache.velocity:velocity ...................... 1.6.4 ->
> 1.7-beta1
>
>
> [INFO] The following plugin updates are available:
> [INFO]   org.codehaus.mojo:exec-maven-plugin .................... 1.2 ->
> 1.2.1
> [INFO]   maven-surefire-plugin ................................... 2.6 ->
> 2.10
> [INFO]   maven-plugin-plugin ...................................... 2.7 ->
> 2.9
> [INFO]   maven-jar-plugin ..................................... 2.3.1 ->
> 2.3.2
> [INFO] maven-antrun-plugin ...................................... 1.3 ->
> 1.6
>
>
>
>
>
>
>
>
>
>
>
>
>
> On 10/7/11 2:11 PM, "Doug Cutting" <[EMAIL PROTECTED]> wrote:
>
>> I'd like to try to release 1.6.0 soon, perhaps making a release
>> candidate next week.  Are there particular issues that folks would like
>> to get into 1.6.0 that are not yet committed?  I hope include AVRO-803.
>>
>> Doug
>

I can open a ticket and submit a patch.

There are a few below that need discussion as well.

-Scott

On 10/17/11 2:18 PM, "Doug Cutting" <[EMAIL PROTECTED]> wrote:

>Scott,
>
>This sounds like a good idea.
>
>Do you want to file an issue and patch for this or should I?
>
>Doug
>
>On 10/15/2011 07:21 PM, Scott Carey wrote:
>> We should consider updating our dependencies where appropriate.
>>
>> * We can use a newer Apache parent project version.
>>
>> Maven versions report:
>> [INFO] The following dependencies in Dependency Management have newer
>> versions:
>> [INFO]   net.sf.jopt-simple:jopt-simple ...................... 3.2 ->
>> 4.0-beta1
>> [INFO]   org.apache.hadoop:hadoop-core ................... 0.20.2 ->
>> 0.20.204.0
>> [INFO]   org.codehaus.jackson:jackson-mapper-asl ............... 1.7.3
>>->
>> 1.9.0
>> [INFO]   org.jboss.netty:netty ..................... 3.2.4.Final ->
>> 3.2.5.Final
>> [INFO]   org.xerial.snappy:snappy-java ..................... 1.0.3.2 ->
>> 1.0.4.1
>>
>>
>> [INFO] The following dependencies in Dependencies have newer versions:
>> [INFO]   junit:junit ............................................ 4.8.2
>>->
>> 4.10
>> [INFO]   org.slf4j:slf4j-api ................................... 1.6.1
>>->
>> 1.6.2
>> [INFO]   org.slf4j:slf4j-simple ................................ 1.6.1
>>->
>> 1.6.2
>> [INFO]   org.apache.maven:maven-plugin-api .................... 2.0.10
>>->
>> 3.0.3
>> [INFO]   org.apache.maven:maven-project ................. 2.0.10 ->
>> 3.0-alpha-2
>> [INFO]   org.apache.ant:ant .................................... 1.7.1
>>->
>> 1.8.2
>> [INFO]   org.apache.velocity:velocity ...................... 1.6.4 ->
>> 1.7-beta1
>>
>>
>> [INFO] The following plugin updates are available:
>> [INFO]   org.codehaus.mojo:exec-maven-plugin .................... 1.2 ->
>> 1.2.1
>> [INFO]   maven-surefire-plugin ................................... 2.6
>>->
>> 2.10
>> [INFO]   maven-plugin-plugin ...................................... 2.7
>>->
>> 2.9
>> [INFO]   maven-jar-plugin ..................................... 2.3.1 ->
>> 2.3.2
>> [INFO] maven-antrun-plugin ...................................... 1.3 ->
>> 1.6
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On 10/7/11 2:11 PM, "Doug Cutting" <[EMAIL PROTECTED]> wrote:
>>
>>> I'd like to try to release 1.6.0 soon, perhaps making a release
>>> candidate next week.  Are there particular issues that folks would like
>>> to get into 1.6.0 that are not yet committed?  I hope include AVRO-803.
>>>
>>> Doug
>>

I think we're very close to making this release.

Please mark any issue that you think can and should make it into 1.6.0
as a Blocker with Fix-Version of 1.6.0 and provide a patch soon.  On
Monday I'll clear the 1.6.0 fix version from non-Blockers.  Once there
are no 1.6.0 Blockers left, I'll roll the release candidate.  With luck
that could happen Monday.

The current blockers are:
  AVRO-935: Update versions of Java dependencies.
  AVRO-930: Memory leak in C.

Thanks,

Doug