[OpenJDK Rasterizer] Marlin #4

[Phil Race]

I think making it *the* default would certainly shake out problems 
better and faster.
Internal testing is mostly done on Oracle JDK builds, not OpenJDK builds.
And if you want to change this from ductus to marlin *after* feature freeze
you will encounter a lot more questions (push back due to invalidated 
testing)
than you would if you wanted to revert later in the face of any hard to 
solve problems.

-phil.

On 10/30/2015 02:34 PM, Jim Graham wrote:
> One question on the integration...
>
> On 10/29/15 4:22 AM, Laurent Bourgès wrote:
>> integration into jdk9 forest:
>> Integration Due:2015-11-27
>>
>> What is the plan according to you ?
>
> Do we want to switch the flag to make Marlin the default before then?
>
> We should probably at least make it the default OpenJDK rasterizer, 
> but what about the production default?
>
> It's something that can be undone later with a single line of code if 
> there are problems so it is probably best to give it maximum exposure 
> as soon as possible by making it the default.  Otherwise we risk 
> nobody using it until the bar for bug fixes gets so low it's hard to 
> get any fixes in...
>
>             ...jim