Can JDK-8210776 be made public? (original) (raw)
Langer, Christoph christoph.langer at sap.com
Thu Nov 21 21:59:49 UTC 2019
- Previous message: Can JDK-8210776 be made public?
- Next message: Can JDK-8210776 be made public?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Phil,
yes, please open it.
It's not so much about the content but the process of backporting would be easier. Then we could place fix-request labels on the bug and backports would get linked to it.
It would be much appreciated.
Thanks Christoph
-----Original Message----- From: jdk-dev <jdk-dev-bounces at openjdk.java.net> On Behalf Of Phil Race Sent: Donnerstag, 21. November 2019 20:01 To: Lindenmaier, Goetz <goetz.lindenmaier at sap.com>; jesper.wilhelmsson at oracle.com Cc: jdk-dev at openjdk.java.net Subject: Re: Can JDK-8210776 be made public?
Hi, I probably could open it, but you'd likely be very disappointed. I am highly doubtful that there will be much that will help with a backport .. The jdk 12 change is already open and I think that is all you need : http://hg.openjdk.java.net/jdk/jdk/rev/8c7638601045 -phil.
On 11/21/19 1:21 AM, Lindenmaier, Goetz wrote: > Hi, > > sorry, resending this to get a thread of it's own. > > Is it possible to open JDK-8210776? > I see that JDK-8230782 was downported to 11.0.6-oracle and > conclude that JDK-8210776 was downported, too. > It would ease downporting if the bug was open. > > Also, thanks JDK-8224505 was opened up! > > Best regards, > Goetz. >>> -----Original Message----- >>> From: jesper.wilhelmsson at oracle.com <jesper.wilhelmsson at oracle.com> >>> Sent: Montag, 4. November 2019 18:06 >>> To: Lindenmaier, Goetz <goetz.lindenmaier at sap.com> >>> Cc: Ioi Lam <ioi.lam at oracle.com>; jdk-dev at openjdk.java.net >>> Subject: Re: JDK-8029528 >>> >>> We have an internal policy saying that any change in the open code should >>> have an open JBS issue, so in theory there shouldn't be any reviews for closed >>> issues on the open lists. If this is happening (enough to be a problem) I'd be >>> happy to take that discussion internally, so please let me know. >>> >>> As for closed bug ids in the problemList this is mainly the result of issues that >>> was moved from closed problemList to open as part of opening different >>> features like JFR, ZGC and others. These bugs should be opened a far as it is >>> possible. I think creating a new open bug and close the old one as a duplicate >> is >>> a good solution if the old bug can't be opened. >>> >>> /Jesper >>>
- Previous message: Can JDK-8210776 be made public?
- Next message: Can JDK-8210776 be made public?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]