I intended it to be the usual minimum of 72 hours - so by Monday. However,
if folks think that we need to extend it due to the holiday period, then we
can do that.
Tom
On Fri, Dec 18, 2015 at 1:04 AM, Sean Busbey wrote:
> what's the voting period on this RC?
>
> On Wed,
+1
* Set the Maven staging as a repo on my system.
* Updated several of my projects that rely heavily on AVRO to use the 1.8.0
version.
* Rebuild and ran all the unit tests on those projects; all passed without
incident
On Wed, Dec 16, 2015 at 6:55 PM, Tom White wrote:
> I
+1
Tom
On Tue, Dec 15, 2015 at 1:08 AM, Ryan Blue wrote:
> I just noticed that our tests are still compiling and running with Java 6.
> Java 7 is already end-of-life (public patches at least), so I think it is
> reasonable to start migrating. Is everyone okay with updating the
+1
On 18 Dec 2015 12:33, "Tom White" wrote:
> +1
>
> Tom
>
> On Tue, Dec 15, 2015 at 1:08 AM, Ryan Blue wrote:
>
> > I just noticed that our tests are still compiling and running with Java
> 6.
> > Java 7 is already end-of-life (public patches at least), so I
Hi,
I'm working on a project where I'm putting Avro records into Kafka and at
the other end pull them out again.
For that purpose I wrote two methods 'toBytes' and 'fromBytes' in a
separate class (see below).
I see this as the type of problem many developers run into.
Would it be a good idea to
I would agree, but unfortunately Java 8 features required bytecode
changes and Java 8 can't be compiled to target Java 7. There is a good
summary of it a few answers down on this SO question:
https://stackoverflow.com/questions/16143684/can-java-8-code-be-compiled-to-run-on-java-7-jvm
I
this would be after 1.8, right?
sounds reasonable, but we should send a [DISCUSS] for impact to user@avro
after the new year to gauge impact on downstream before we decide.
On Mon, Dec 14, 2015 at 7:08 PM, Ryan Blue wrote:
> I just noticed that our tests are still compiling