P3
Since using SKARA for jdk11u-dev, we've noticed that we no longer can use Oracle JDK 11u fixed bugs a ref for OpenJDK equivalents. Example bug here:
https://bugs.openjdk.java.net/browse/JDK-8251945
Pre-skara we'd just use "8251945: SIGSEGV in PackageEntry::purge_qualified_exports()" in the commit message and HG-updater would have been smart enough to create a backport bug on push.
With Skara we end up having the problem of needing a <sha> to reference. But those are hidden for Oracle JDK 11/8 bugs. If somebody was to create a PR referencing the already closed issue, bots would complain with "Issue is not open." warning. What's more, the PR gets linked as "Review" in the closed bug. Example PR:
https://github.com/openjdk/jdk11u-dev/pull/22
We'd need some alternative way to use such bugs for creating a backport using Skara.
https://bugs.openjdk.java.net/browse/JDK-8251945
Pre-skara we'd just use "8251945: SIGSEGV in PackageEntry::purge_qualified_exports()" in the commit message and HG-updater would have been smart enough to create a backport bug on push.
With Skara we end up having the problem of needing a <sha> to reference. But those are hidden for Oracle JDK 11/8 bugs. If somebody was to create a PR referencing the already closed issue, bots would complain with "Issue is not open." warning. What's more, the PR gets linked as "Review" in the closed bug. Example PR:
https://github.com/openjdk/jdk11u-dev/pull/22
We'd need some alternative way to use such bugs for creating a backport using Skara.
