2015-02-20 1:08 GMT+01:00 Phil Race <philip.r...@oracle.com>: > If there was initially zero impact on any production code I can see that > being > more acceptable but I don't understand why its a problem to demonstrate > this by putting it in an OpenJDK Project sandbox and thereby be something > we can build so that JCK and SQE could look at it first - pisces is after > all > part of the RI used to pass TCK, and sometimes there's a performance > vs spec. adherence trade off in what we do. >
Hi Phil, I think there is a communication problem here, it's perfectly fine and acceptable to put this under an OpenJDK Project sandbox, and in fact it makes all sense. The argument is on actually doing it and starting this process, so far every time Laurent has been told something different and when he approached to start it, somebody (as authoritative as it can possibly be!) told him something different. Indeed, his contribution is pretty big, probably the biggest external contribution since a lot of time, and is difficult to handle that, but it seems to be also rather important. So the question now is what it needs for Marlin to get started as part of the Rasterizer Project perhaps, but finally moving the discussion away from the Process, and toward the merit of the actual code. Btw, I'm happy that *you* replied, this hopefully means this step is finally starting! :) Cheers, Mario -- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF Java Champion - Blog: http://neugens.wordpress.com - Twitter: @neugens Proud GNU Classpath developer: http://www.classpath.org/ OpenJDK: http://openjdk.java.net/projects/caciocavallo/ Please, support open standards: http://endsoftpatents.org/
