JDK submit repo
dalibor.topic at oracle.com
Fri Jan 26 16:40:32 UTC 2018
On 24.01.2018 17:17, mark.reinhold at oracle.com wrote:
>> Instead, I would suggest explicitly advising Comitters with test
>> failures to forward them to the jdk-dev mailing list in search of an
>> Oracle engineer.
> Please, no. Asking jdk-dev should be the option of last resort. If
> you're working on a fix for something then you've hopefully already
> discussed it on the appropriate list. I agree that we should make it
> easier for newcomers to figure out which list to go to, but spamming
> jdk-dev is not the answer.
Yeah, documenting how to go from 'something failed' to finding the right
list to post to as part of the wiki (or ideally, as part of the e-mail
being sent out - a URL to a separate page on the wiki describing what
steps to follow to find the right mailing list to contact) would be
I think in the longer term, it would be useful for JDK and JDK Updates
to consider adopting a mechanism similar to the Maintainers file the
Linux kernel uses to delineate source code areas with their respective
mailing lists to contact.
That way instructions such as the above could become rather simple, and
ripe for further automation.
<http://www.oracle.com> Dalibor Topic | Principal Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg
ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
<http://www.oracle.com/commitment> Oracle is committed to developing
practices and products that help protect the environment
More information about the jdk-dev