Re: [DISCUSS] Community engagement

On Mon, Nov 14, 2016 at 8:40 PM, Ryan Blue wrote: > we don't have enough votes for a release I don't think that's true. You might not have gotten enough votes within a few days. I too have had that problem for several releases. But when that happened I would send personal messages to a few PMC

[jira] [Commented] (AVRO-1906) C: allow file with no records

[ https://issues.apache.org/jira/browse/AVRO-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668064#comment-15668064 ] ASF GitHub Bot commented on AVRO-1906: -- GitHub user walshb opened a pull request:

[GitHub] avro pull request #160: AVRO-1906: C: Allow file with no records.

GitHub user walshb opened a pull request: https://github.com/apache/avro/pull/160 AVRO-1906: C: Allow file with no records. You can merge this pull request into a Git repository by running: $ git pull https://github.com/walshb/avro avro-1906-file-no-records Alternatively you

[GitHub] avro pull request #159: AVRO-1904: C: Allow record to have no fields.

GitHub user walshb opened a pull request: https://github.com/apache/avro/pull/159 AVRO-1904: C: Allow record to have no fields. You can merge this pull request into a Git repository by running: $ git pull https://github.com/walshb/avro avro-1904-record-no-fields Alternatively

[jira] [Commented] (AVRO-1904) C: record with no fields should be allowed

[ https://issues.apache.org/jira/browse/AVRO-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668063#comment-15668063 ] ASF GitHub Bot commented on AVRO-1904: -- GitHub user walshb opened a pull request:

[jira] [Commented] (AVRO-1902) C: namespace "" should mean namespace = NULL

[ https://issues.apache.org/jira/browse/AVRO-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668060#comment-15668060 ] ASF GitHub Bot commented on AVRO-1902: -- GitHub user walshb opened a pull request:

[GitHub] avro pull request #158: AVRO-1902: C: Namespace "" means space = NULL.

GitHub user walshb opened a pull request: https://github.com/apache/avro/pull/158 AVRO-1902: C: Namespace "" means space = NULL. You can merge this pull request into a Git repository by running: $ git pull https://github.com/walshb/avro avro-1902-c-namespace-null Alternativel

[jira] [Commented] (AVRO-1542) std::auto_ptr

[ https://issues.apache.org/jira/browse/AVRO-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667573#comment-15667573 ] ASF GitHub Bot commented on AVRO-1542: -- GitHub user sanjosh opened a pull request:

Re: changing auto_ptr to unique_ptr

found existing jira https://issues.apache.org/jira/browse/AVRO-1542 and sent pull request https://github.com/apache/avro/pull/157 On Tue, Nov 15, 2016 at 9:43 PM, suraj acharya wrote: > Yeah the instructions are up-to date. > File a jira if it doesn't already exist. > > S > > > On Tue, Nov 15,

[GitHub] avro pull request #157: AVRO-1542 replacing auto_ptr by unique_ptr & std::mo...

GitHub user sanjosh opened a pull request: https://github.com/apache/avro/pull/157 AVRO-1542 replacing auto_ptr by unique_ptr & std::move Please verify 1) addition of flags to CMakeLists.txt and 2) one case where auto_ptr was being passed by reference but is now change

Re: changing auto_ptr to unique_ptr

Yeah the instructions are up-to date. File a jira if it doesn't already exist. S On Tue, Nov 15, 2016 at 10:02 AM, Sandeep Joshi wrote: > Hi, > > I'd like to submit a pull request/patch to change all auto_ptr in lang/c++ > to unique_ptr. > > I assume the instructions here as still up-to-date >

changing auto_ptr to unique_ptr

Hi, I'd like to submit a pull request/patch to change all auto_ptr in lang/c++ to unique_ptr. I assume the instructions here as still up-to-date https://cwiki.apache.org/confluence/display/AVRO/How+To+Contribute Can I go ahead and send a pull request ? -Sandeep

Re: [DISCUSS] Community engagement

I'm not at all convinced that splitting the project into per-language pieces will help. It will be a lot of work and I think we'll just get lots of orphaned languages that never get released. When I did the 1.8.0 release I had to fix a few failing tests for a couple of languages, but it was mainly

Re: [DISCUSS] Community engagement

Hi, I may have been ambiguous in my suggestion about the mailing lists. I did not intend to suggest separating mailing lists for the different language bindings. What I would like to separate from each other instead are real discussions and automated notifications (JIRAs, pull request, etc.). Zol