On 3/11/2019 3:49 PM, Mandy Chung wrote:
On 3/11/19 8:48 AM, Adam Farley8 wrote:
Hi Mandy,
Thank you for explaining. :)
Unfortunately I'm only a mere Author, and I cannot submit test runs
on the shared test server.
I have run the test locally, and it passes against a patched build
and fails correctly agaionst an unpatched build, so I think we're
good to go.
I will sponsor this patch for you when CSR is approved.
Can you tell me if there's something I can do to help move the CSR
forward?
No additional action from your end. It's already in finalized state.
Also, can you tell me if an additional CSR would need to be created
for other releases if this fix gets backported?
Which release are you thinking to backport to?
IMO I don't think this fix is critical for existing releases
and this fix has behavioral change.
As a procedural matter, to do a CSR for multiple releases, first create
the backport issue for the release or release train in question (e.g.
some particular update release like "12.0.1" or "12-pool") and then
create a CSR of the backport. This is the procedure if an update release
train is using the CSR review process.
However, note that as this proposed changes alters a spec in the Java SE
API, it would require a maintenance review of the Java SE spec, which is
very unlikely to occur in an update release.
HTH,
-Joe
