<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><span class=""><blockquote type="cite"><div><br>
</div>
<div>But seriously: SAP is supporting CMS and will probably do so
for quite a long time (simply because we do support old Java
releases for a very long time).</div>
</blockquote>
<blockquote type="cite">
<div><br>
</div>
<div>Completely removing CMS from the HotSpot code base may
increase these support costs considerably for us.</div>
<div><br>
</div>
<div>Do you plan to really delete the sources from the repos or do
you only plan to disable it at build time?</div>
</blockquote>
<br></span>
I just don't know how this is going to play out. I expect that the
OpenJDK community <br>
will want the sources to stay. In such a case Oracle would want
them segregated sufficiently<br>
that we don't build the the sources. <br><span class="">
<br>
<blockquote type="cite">I think only disable it at build time would make it
easier for us and others to still support it in the future. But in
that case we really have to come up with a better development
model which would allow external developers to directly push CMS
changes (much like ppc64 or aarch64 changes). Everything else
would be a real PITA.</blockquote>
<br></span>
I think some model like ppc64/aarch64 would be a good way to go.
That would be a<br>
nice side effect of this change. You know better than I on how to
get there. <br></div></blockquote><div><br></div><div>We also need to support CMS perhaps for a long time. I like the idea of segregating it, and have more external developers contribute to it.</div><div>Is there any document or can anyone explain to me how ppc64/arch64 works?</div><div>In such case, who is responsible for code review, building, testing, release and so on?</div><div><br></div></div>
</div></div>