Duplicate bug ID blocking integration (original) (raw)

Joseph D. Darcy joe.darcy at oracle.com
Tue Jun 27 21:20:14 UTC 2017

Per previous discussions [1], the unique bug id check is planned to be disabled when the repository consolidation occurs (update on that project coming soon).

I see no harm in disabling the duplicate bug id check in JDK 10 a bit earlier, say right now.

Cheers,

-Joe

[1] http://mail.openjdk.java.net/pipermail/jdk10-dev/2017-April/000152.html

On 6/27/2017 1:40 PM, jesper.wilhelmsson at oracle.com wrote:

Hi,

Another change has been pushed to both JDK 9 and JDK 10 using different changesets with the same bug id. The fix from 9 has been automatically forwardported to 10, and since the JDK 10 fix was pushed to 10/hs we are now blocked from integrating 10/10 changes to 10/hs. The last time this happened it was suggested that removing the duplicate id check might be a better option than to whitelist the change. What is the timeline for removing the duplicate id check? Thanks, /Jesper

More information about the jdk10-dev mailing list