Re: [DISCUSS] Community engagement

2016-11-13 Thread Simon Woodford
Hi all, CI testing seems an excellent idea. So does splitting the languages for releasing. If the languages are split then I think it would be a good idea to have separate mailing lists so that e.g.C++ devs don't get all the Java pull requests. That should make review and commit turnaround times

Re: [DISCUSS] Community engagement

2016-11-13 Thread Anders Sundelin
Hi Ryan, I am new in this community, so please take my comments with that in mind :-) The idea of splitting implementations seems very logical to me, but I think that, as Avro is a serialization framework, there would have to be integration tests that take into account that the byte-level imp

[DISCUSS] Community engagement

2016-11-13 Thread Ryan Blue
Hi everyone, We tried to release Avro 1.8.2 this week, but the release vote failed because only two PMC members voted on the candidate and we didn't have enough binding votes to pass. There was a minor problem (in my opinion) with the candidate that could have been the reason why there weren't mor