Thanks for responding, everyone!
First, on the subject of the Attic: I don't think Avro is headed to the
Attic soon, but I think that the current level of engagement is too low to
refresh the active part of the community -- we don't have enough votes for
a release and it takes a long time for
I disagree that Avro is heading towards the Attic. Its rate of
contribution has been slow but steady for years. That's the nature of
this project. It had a larger number of contributions in its first
few years, when new languages and substantial features were being
added, but since then, we see
[
https://issues.apache.org/jira/browse/AVRO-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clément MATHIEU updated AVRO-1960:
--
Attachment: AVRO-1960.patch
This simple log4j.properties file replicates the one provided by
Clément MATHIEU created AVRO-1960:
-
Summary: avro-tools should not display log4j warning when started
with java -jar
Key: AVRO-1960
URL: https://issues.apache.org/jira/browse/AVRO-1960
Project: Avro
Hi,
I agree that there is a delay in code reviews and that is one reason for
the decline in participation.
Regarding the testing I agree we are a bit shorthanded. We need to setup
pre-commit tests and run some more testing regularly.
I agree with your problem of docker and I have seen the same
Hi,
I agree with the proposed changes.
Regarding the mailing lists, I would like to suggest to separate not only
the different languages from each other, but also the discussions from the
pull requests, test results and JIRA notifications. When those are mixed
together, discussions easily get
