From alex.buckley at oracle.com Wed May 1 00:50:47 2019 From: alex.buckley at oracle.com (Alex Buckley) Date: Tue, 30 Apr 2019 17:50:47 -0700 Subject: Draft JEP: Keyword Management for the Java Language Message-ID: <5CC8ED67.6060008@oracle.com> Evolving the Java language often means new keywords for new features, but new keywords risk breaking existing programs. In the Project Amber expert group, Brian Goetz suggested a technique for generating new keywords that balances compatibility and readability -- _hyphenated keywords_ -- and there is already a language feature raring to use it (JEP 354, Switch Expressions). We have now produced an Informational JEP to record the intent and detail of hyphenated keywords, for Feature JEPs may rely on. It also captures a policy for managing (that is, stewarding) Java's keywords more broadly. Your comments are welcome. https://bugs.openjdk.java.net/browse/JDK-8223002 Alex From john.r.rose at oracle.com Wed May 1 01:33:46 2019 From: john.r.rose at oracle.com (John Rose) Date: Tue, 30 Apr 2019 18:33:46 -0700 Subject: Draft JEP: Keyword Management for the Java Language In-Reply-To: <5CC8ED67.6060008@oracle.com> References: <5CC8ED67.6060008@oracle.com> Message-ID: <2D88C340-3782-4CDC-8EBC-EC3C44F2A140@oracle.com> On Apr 30, 2019, at 5:50 PM, Alex Buckley wrote: > > Evolving the Java language often means new keywords for new features, but new keywords risk breaking existing programs. In the Project Amber expert group, Brian Goetz suggested a technique for generating new keywords that balances compatibility and readability -- _hyphenated keywords_ -- and there is already a language feature raring to use it (JEP 354, Switch Expressions). > > We have now produced an Informational JEP to record the intent and detail of hyphenated keywords, for Feature JEPs may rely on. It also captures a policy for managing (that is, stewarding) Java's keywords more broadly. Your comments are welcome. > > https://bugs.openjdk.java.net/browse/JDK-8223002 Bravo. That's a very good account of a tricky subject. ? John From yumin.qi at gmail.com Wed May 1 02:26:22 2019 From: yumin.qi at gmail.com (yumin qi) Date: Tue, 30 Apr 2019 19:26:22 -0700 Subject: Draft JEP: Socket API for Remote Direct Memory Access (RDMA) In-Reply-To: <9ACD5B67AAC5594CB6268234CF29CF9AD140CE19@ORSMSX113.amr.corp.intel.com> References: <9ACD5B67AAC5594CB6268234CF29CF9AD1409AF5@ORSMSX113.amr.corp.intel.com> <9ACD5B67AAC5594CB6268234CF29CF9AD140CE19@ORSMSX113.amr.corp.intel.com> Message-ID: Hi, Yingqi Have you integrated RDMA implementation into jdk13? I haven't seen messages related to this JEP since the last email in this thread. Thanks Yumin On Mon, May 21, 2018 at 8:37 AM Lu, Yingqi wrote: > Hi Chris, > > Thank you for the feedback. > > Yes, on the platform that does not support rsocket, UOE is thrown. I will > make it clear in the document. > > I will modify the reference links too. > > Thanks, > Lucy > > >-----Original Message----- > >From: Chris Hegarty [mailto:chris.hegarty at oracle.com] > >Sent: Monday, May 21, 2018 3:42 AM > >To: Lu, Yingqi ; jdk-dev at openjdk.java.net > >Cc: Viswanathan, Sandhya ; Aundhe, > >Shirish ; nio-dev at openjdk.java.net; Kaczmarek, > >Eric > >Subject: Re: Draft JEP: Socket API for Remote Direct Memory Access (RDMA) > > > >Hi Lucy, > > > >On 18/05/18 19:21, Lu, Yingqi wrote: > >> Hi All, > >> > >> We just submitted a JEP draft > >> https://bugs.openjdk.java.net/browse/JDK-8203434. The proposal is to > >> enhance the Java Socket API to support Remote Direct Memory Access > >> (RDMA) using the rsocket protocol on the Linux-based platforms. > > > >This latest version looks very good. Just a few minor minor comments that > I > >did not noticed before. > > > >1) What is the behavior on platforms that do not support RDMA? > > For example, will jdk.net.Sockets::openRdmaSocketChannel > > throw UnsupportedOperationException? If so, then maybe make > > that clear in the API sketch in the description. > > > >2) Links to external references seem to have been inadvertently > > dropped. Prefer markdown links, e.g. > > > > ... form [Wikipedia][wikirdma] ... > > > > [wikirdma]: > https://en.wikipedia.org/wiki/Remote_direct_memory_access > > > >-Chris. > From Alan.Bateman at oracle.com Wed May 1 06:06:18 2019 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Wed, 1 May 2019 07:06:18 +0100 Subject: Draft JEP: Socket API for Remote Direct Memory Access (RDMA) In-Reply-To: References: <9ACD5B67AAC5594CB6268234CF29CF9AD1409AF5@ORSMSX113.amr.corp.intel.com> <9ACD5B67AAC5594CB6268234CF29CF9AD140CE19@ORSMSX113.amr.corp.intel.com> Message-ID: <7822f79b-0ee2-73b8-a876-26b1c5de6df2@oracle.com> On 01/05/2019 03:26, yumin qi wrote: > Hi, Yingqi > > Have you integrated RDMA implementation into jdk13? I haven't seen > messages related to this JEP since the last email in this thread. > The JEP is a candidate [1], not targeted to any release yet (so not integrated). The discussion on this feature is on the nio-dev mailing list (there are hundreds of mails but you should be able to catch up via the archives). The main blocking issues right now are bugs in the Linux RDMA support [1]. One of the Intel committers on that project has PRs to fix those issues so the development should be able to continue. -Alan [1] https://openjdk.java.net/jeps/337 [2] https://github.com/linux-rdma/rdma-core From forax at univ-mlv.fr Wed May 1 12:07:11 2019 From: forax at univ-mlv.fr (Remi Forax) Date: Wed, 1 May 2019 14:07:11 +0200 (CEST) Subject: Draft JEP: Keyword Management for the Java Language In-Reply-To: <5CC8ED67.6060008@oracle.com> References: <5CC8ED67.6060008@oracle.com> Message-ID: <1092732121.508230.1556712431993.JavaMail.zimbra@u-pem.fr> Thanks for this write-up, two remarks, - for the constraints on hyphenated keywords, using int-typed expressions is perhaps a little too clever because the compiler has to provide meaningful error message for the user (and IDEs automatic completion of not yet fully form expressions), by example, if there is an hyphenated keyword new-fun, for the snippet return A::new-fun, the expression is not valid but there are two interpretations A::new - fun or A:: new-fun. I think it's better to use a grammar approach (which keywords can be at left side or right side of an expression). Also the current rule doesn't work well if in the future we want to introduce operator overloading. - the example total-switch in section "hyphenated keywords" is invalid given the constraints you give. regards, R?mi ----- Mail original ----- > De: "Alex Buckley" > ?: "jdk-dev" > Envoy?: Mercredi 1 Mai 2019 02:50:47 > Objet: Draft JEP: Keyword Management for the Java Language > Evolving the Java language often means new keywords for new features, > but new keywords risk breaking existing programs. In the Project Amber > expert group, Brian Goetz suggested a technique for generating new > keywords that balances compatibility and readability -- _hyphenated > keywords_ -- and there is already a language feature raring to use it > (JEP 354, Switch Expressions). > > We have now produced an Informational JEP to record the intent and > detail of hyphenated keywords, for Feature JEPs may rely on. It also > captures a policy for managing (that is, stewarding) Java's keywords > more broadly. Your comments are welcome. > > https://bugs.openjdk.java.net/browse/JDK-8223002 > > Alex From mbien42 at gmail.com Wed May 1 15:27:27 2019 From: mbien42 at gmail.com (Michael Bien) Date: Wed, 1 May 2019 17:27:27 +0200 Subject: JEP proposed to target JDK 13: 350: Dynamic CDS Archives In-Reply-To: <20190425212613.B336F28837B@eggemoggin.niobe.net> References: <20190425212613.B336F28837B@eggemoggin.niobe.net> Message-ID: since each JVM process would create its own dynamic class data archive, on top of a static archive, i would assume that only the static archive would be shared between processes, while the dynamic archive would be mostly only beneficial for tuning startup time. Manually created static AppCDS archives on the other hand are fully shareable and can help with both, footprint and startup time. Would this be correct or is more sharing magic going on between those per-process archives? (i suppose you could just use the dynamic CDS feature once and use the dynamic archive just like it would be a second static & shareable archive) best regards, michael On 25.04.19 23:26, mark.reinhold at oracle.com wrote: > The following JEP is proposed to target JDK 13: > > 350: Dynamic CDS Archives > https://openjdk.java.net/jeps/350 > > Feedback on this proposal from JDK Project Committers and Reviewers [1] > is more than welcome, as are reasoned objections. If no such objections > are raised by 23:00 UTC on Thursday, 2 May, or if they?re raised and > then satisfactorily answered, then per the JEP 2.0 process proposal [2] > I?ll target this JEP to JDK 13. > > - Mark > > > [1] https://openjdk.java.net/census#jdk > [2] https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html From jianglizhou at google.com Wed May 1 16:47:52 2019 From: jianglizhou at google.com (Jiangli Zhou) Date: Wed, 1 May 2019 09:47:52 -0700 Subject: JEP proposed to target JDK 13: 350: Dynamic CDS Archives In-Reply-To: References: <20190425212613.B336F28837B@eggemoggin.niobe.net> Message-ID: On Wed, May 1, 2019 at 8:25 AM Michael Bien wrote: > > since each JVM process would create its own dynamic class data archive, > on top of a static archive, i would assume that only the static archive > would be shared between processes, while the dynamic archive would be > mostly only beneficial for tuning startup time. > > Manually created static AppCDS archives on the other hand are fully > shareable and can help with both, footprint and startup time. With the traditional static archiving technology, memory sharing is achieved when the same archived classes and shareable java objects are loaded&used in different JVM processes. This is still the same for dynamic archiving. The memory sharing benefit with base_archive/dynamic_archive would be the same as a single static archive when running the same Java application in different JVM instances (on the same host). Best, Jiangli > > Would this be correct or is more sharing magic going on between those > per-process archives? > > (i suppose you could just use the dynamic CDS feature once and use the > dynamic archive just like it would be a second static & shareable archive) > > best regards, > michael > > On 25.04.19 23:26, mark.reinhold at oracle.com wrote: > > The following JEP is proposed to target JDK 13: > > > > 350: Dynamic CDS Archives > > https://openjdk.java.net/jeps/350 > > > > Feedback on this proposal from JDK Project Committers and Reviewers [1] > > is more than welcome, as are reasoned objections. If no such objections > > are raised by 23:00 UTC on Thursday, 2 May, or if they?re raised and > > then satisfactorily answered, then per the JEP 2.0 process proposal [2] > > I?ll target this JEP to JDK 13. > > > > - Mark > > > > > > [1] https://openjdk.java.net/census#jdk > > [2] https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html > > From ioi.lam at oracle.com Wed May 1 16:53:23 2019 From: ioi.lam at oracle.com (Ioi Lam) Date: Wed, 1 May 2019 09:53:23 -0700 Subject: JEP proposed to target JDK 13: 350: Dynamic CDS Archives In-Reply-To: References: <20190425212613.B336F28837B@eggemoggin.niobe.net> Message-ID: The dynamic archive can also be shared across processes running on the same host, as long as they are running the same program. So if you're running multiple copies of the same program, then using the old method (single static archive) is roughly the same as the new method (static archive + dynamic archive). If your environment runs different programs that share the same set of libraries. e.g., ? ? 2 processes running with "-cp:lib.jar:foo.jar FooApp" ? ? 4 processes running with "-cp:lib.jar:bar.jar BarApp" to achieve best sharing, you can create a static archive (using a classlist) for only the classes in lib.jar (and any other system classes used by these apps). Then, create two different dynamic archives, one for the "foo" app, and the other for the "bar" app. This way, the static archive can be shared across all 6 processes, and the dynamic archives can be shared among the processes running the same program. Thanks - Ioi On 5/1/19 8:27 AM, Michael Bien wrote: > since each JVM process would create its own dynamic class data > archive, on top of a static archive, i would assume that only the > static archive would be shared between processes, while the dynamic > archive would be mostly only beneficial for tuning startup time. > > Manually created static AppCDS archives on the other hand are fully > shareable and can help with both, footprint and startup time. > > Would this be correct or is more sharing magic going on between those > per-process archives? > > (i suppose you could just use the dynamic CDS feature once and use the > dynamic archive just like it would be a second static & shareable > archive) > > best regards, > michael > > On 25.04.19 23:26, mark.reinhold at oracle.com wrote: >> The following JEP is proposed to target JDK 13: >> >> ?? 350: Dynamic CDS Archives >> ??????? https://openjdk.java.net/jeps/350 >> >> Feedback on this proposal from JDK Project Committers and Reviewers [1] >> is more than welcome, as are reasoned objections.? If no such objections >> are raised by 23:00 UTC on Thursday, 2 May, or if they?re raised and >> then satisfactorily answered, then per the JEP 2.0 process proposal [2] >> I?ll target this JEP to JDK 13. >> >> - Mark >> >> >> [1] https://openjdk.java.net/census#jdk >> [2] https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html > > From mbien42 at gmail.com Wed May 1 19:02:46 2019 From: mbien42 at gmail.com (Michael Bien) Date: Wed, 1 May 2019 21:02:46 +0200 Subject: JEP proposed to target JDK 13: 350: Dynamic CDS Archives In-Reply-To: References: <20190425212613.B336F28837B@eggemoggin.niobe.net> Message-ID: Thank you very much for the detailed explanation Jiangli and Ioi. On Wed, May 1, 2019 at 6:53 PM Ioi Lam wrote: > The dynamic archive can also be shared across processes running on the > same host, as long as they are running the same program. > > So if you're running multiple copies of the same program, then using the > old method (single static archive) is roughly the same as the new method > (static archive + dynamic archive). > > If your environment runs different programs that share the same set of > libraries. e.g., > > 2 processes running with "-cp:lib.jar:foo.jar FooApp" > 4 processes running with "-cp:lib.jar:bar.jar BarApp" > > to achieve best sharing, you can create a static archive (using a > classlist) for only the classes in lib.jar (and any other system classes > used by these apps). Then, create two different dynamic archives, one > for the "foo" app, and the other for the "bar" app. > Understood. My main confusion came from the fact that i thought that each FooApp process was supposed to create its own dynamic archive based on the last run of the program. But FooApp and BarApp should just have two different dynamic archives, not six (one for each process). Will -XX:ArchiveClassesAtExit=dynfoo.jsa skip archive creation if the file already exists? Or is this flag only intended for the initial setup run of a program? > > This way, the static archive can be shared across all 6 processes, and > the dynamic archives can be shared among the processes running the same > program. > > Thanks > - Ioi > > > On 5/1/19 8:27 AM, Michael Bien wrote: > > since each JVM process would create its own dynamic class data > > archive, on top of a static archive, i would assume that only the > > static archive would be shared between processes, while the dynamic > > archive would be mostly only beneficial for tuning startup time. > > > > Manually created static AppCDS archives on the other hand are fully > > shareable and can help with both, footprint and startup time. > > > > Would this be correct or is more sharing magic going on between those > > per-process archives? > > > > (i suppose you could just use the dynamic CDS feature once and use the > > dynamic archive just like it would be a second static & shareable > > archive) > > > > best regards, > > michael > > > > On 25.04.19 23:26, mark.reinhold at oracle.com wrote: > >> The following JEP is proposed to target JDK 13: > >> > >> 350: Dynamic CDS Archives > >> https://openjdk.java.net/jeps/350 > >> > >> Feedback on this proposal from JDK Project Committers and Reviewers [1] > >> is more than welcome, as are reasoned objections. If no such objections > >> are raised by 23:00 UTC on Thursday, 2 May, or if they?re raised and > >> then satisfactorily answered, then per the JEP 2.0 process proposal [2] > >> I?ll target this JEP to JDK 13. > >> > >> - Mark > >> > >> > >> [1] https://openjdk.java.net/census#jdk > >> [2] https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html > > > > > > From alex.buckley at oracle.com Wed May 1 19:22:10 2019 From: alex.buckley at oracle.com (Alex Buckley) Date: Wed, 01 May 2019 12:22:10 -0700 Subject: Draft JEP: Keyword Management for the Java Language In-Reply-To: <1092732121.508230.1556712431993.JavaMail.zimbra@u-pem.fr> References: <5CC8ED67.6060008@oracle.com> <1092732121.508230.1556712431993.JavaMail.zimbra@u-pem.fr> Message-ID: <5CC9F1E2.5040000@oracle.com> Remi, thanks for your comments. On 5/1/2019 5:07 AM, Remi Forax wrote: > - for the constraints on hyphenated keywords, using int-typed > expressions is perhaps a little too clever because the compiler has > to provide meaningful error message for the user (and IDEs automatic > completion of not yet fully form expressions), by example, if there > is an hyphenated keyword new-fun, for the snippet return A::new-fun, > the expression is not valid but there are two interpretations A::new > - fun or A:: new-fun. I think it's better to use a grammar approach > (which keywords can be at left side or right side of an expression). > Also the current rule doesn't work well if in the future we want to > introduce operator overloading. I had some trouble understanding "using int-typed expressions is perhaps a little too clever", because they're just examples to make a point, while "a little too clever" is the kind of comment usually targeted at a fundamental design decision. I think what you mean is "a little too limiting". To spell it all out: 1. Type-correct expressions that perform subtraction are part of the "overlap" with hyphenated keywords; and 2. Type-incorrect statements that complete abruptly are part of the overlap too (`throw-quickly` is syntactically valid today -- it will lex and parse if `quickly` is a numeric variable -- but it is also semantically invalid (type error), so we COULD reclassify it as a hyphenated keyword, but we have ALREADY decided not to, per how `throw` is mentioned in set A); and 3. [Remi's observation] Type-incorrect expressions that perform subtraction are part of the overlap too (`A::new-fun` is syntactically valid today, but semantically invalid, so we COULD reclassify it as a hyphenated keyword, but we should be consistent with #2 and forbid `new-*` hyphenated keywords like we do for `throw-*`). (You also raise the point that if the `-` operator could be overloaded, then it might be semantically valid for the left operand to be a method reference expression involving `::new`, and that would clash super-badly with `new-*` hyphenated keywords.) tl;dr I will add `new` to set A, and avoid so much focus there on int-typed expressions. > - the example total-switch in section "hyphenated keywords" is > invalid given the constraints you give. Oops! Removed. Alex From john.r.rose at oracle.com Wed May 1 19:46:46 2019 From: john.r.rose at oracle.com (John Rose) Date: Wed, 1 May 2019 12:46:46 -0700 Subject: Draft JEP: Keyword Management for the Java Language In-Reply-To: <1092732121.508230.1556712431993.JavaMail.zimbra@u-pem.fr> References: <5CC8ED67.6060008@oracle.com> <1092732121.508230.1556712431993.JavaMail.zimbra@u-pem.fr> Message-ID: On May 1, 2019, at 5:07 AM, Remi Forax wrote: > > the current rule doesn't work well if in the future we want to introduce operator overloading. This sort of thing is unavoidable in language evolution, isn't it? Any future extension will have to avoid ground already taken by past extensions. If we reserve the space of hyphenated keywords this year, and introduce new kinds of expressions involving hyphen next year, it follows that code written next year must avoid accidentally mentioning hyphenated keywords. Luckily that's pretty easy: Just put one or more whitespace characters near the hyphen, so that it can be a minus sign (or whatever other job our future selves dream up for it). One nice thing about Alex's proposal is that, if adopted this year, IDEs can immediately syntax-color all possible hyphenated proper keywords (and maybe even most of the conditional ones). Linguists call this sort of scheme "generative", in that you can coin new words, within the scheme, and their usage is somewhat clear even if they have never been seen before. Example from English (from Greek): "Xgenic" describes a source of some X, so although the term "lexigenic" is not in common use, but you probably guess a meaning for it, some kind of source of "lex". This particular term might serve to describe a lexical rule that generates new lexemes, such as Alex's lexigenic proposal. ? John From ioi.lam at oracle.com Wed May 1 19:51:51 2019 From: ioi.lam at oracle.com (Ioi Lam) Date: Wed, 1 May 2019 12:51:51 -0700 Subject: JEP proposed to target JDK 13: 350: Dynamic CDS Archives In-Reply-To: References: <20190425212613.B336F28837B@eggemoggin.niobe.net> Message-ID: On 5/1/19 12:02 PM, Michael Bien wrote: > Thank you very much for the detailed explanation Jiangli and Ioi. > > On Wed, May 1, 2019 at 6:53 PM Ioi Lam wrote: > >> The dynamic archive can also be shared across processes running on the >> same host, as long as they are running the same program. >> >> So if you're running multiple copies of the same program, then using the >> old method (single static archive) is roughly the same as the new method >> (static archive + dynamic archive). >> >> If your environment runs different programs that share the same set of >> libraries. e.g., >> >> 2 processes running with "-cp:lib.jar:foo.jar FooApp" >> 4 processes running with "-cp:lib.jar:bar.jar BarApp" >> >> to achieve best sharing, you can create a static archive (using a >> classlist) for only the classes in lib.jar (and any other system classes >> used by these apps). Then, create two different dynamic archives, one >> for the "foo" app, and the other for the "bar" app. >> > Understood. My main confusion came from the fact that i thought that each > FooApp process was supposed to create its own dynamic archive based on the > last run of the program. But FooApp and BarApp should just have two > different dynamic archives, not six (one for each process). > > Will -XX:ArchiveClassesAtExit=dynfoo.jsa skip archive creation if the file > already exists? Or is this flag only intended for the initial setup run of > a program? Currently, the -XX:ArchiveClassesAtExit=dynfoo.jsa option works the same way as in the old "static dump" where you would specify -Xshare:dump -XX:SharedArchiveFile=xyz.jsa. If the file exists, it will be overwritten. So in this usage model, there's a distinct "setup" phase where you create the archive. We are considering making the dynamic dumping more automatic in an future RFE. Thanks - Ioi > >> This way, the static archive can be shared across all 6 processes, and >> the dynamic archives can be shared among the processes running the same >> program. >> >> Thanks >> - Ioi >> >> >> On 5/1/19 8:27 AM, Michael Bien wrote: >>> since each JVM process would create its own dynamic class data >>> archive, on top of a static archive, i would assume that only the >>> static archive would be shared between processes, while the dynamic >>> archive would be mostly only beneficial for tuning startup time. >>> >>> Manually created static AppCDS archives on the other hand are fully >>> shareable and can help with both, footprint and startup time. >>> >>> Would this be correct or is more sharing magic going on between those >>> per-process archives? >>> >>> (i suppose you could just use the dynamic CDS feature once and use the >>> dynamic archive just like it would be a second static & shareable >>> archive) >>> >>> best regards, >>> michael >>> >>> On 25.04.19 23:26, mark.reinhold at oracle.com wrote: >>>> The following JEP is proposed to target JDK 13: >>>> >>>> 350: Dynamic CDS Archives >>>> https://openjdk.java.net/jeps/350 >>>> >>>> Feedback on this proposal from JDK Project Committers and Reviewers [1] >>>> is more than welcome, as are reasoned objections. If no such objections >>>> are raised by 23:00 UTC on Thursday, 2 May, or if they?re raised and >>>> then satisfactorily answered, then per the JEP 2.0 process proposal [2] >>>> I?ll target this JEP to JDK 13. >>>> >>>> - Mark >>>> >>>> >>>> [1] https://openjdk.java.net/census#jdk >>>> [2] https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html >>> >> From raymond.gallardo at oracle.com Wed May 1 20:13:21 2019 From: raymond.gallardo at oracle.com (Raymond Gallardo) Date: Wed, 1 May 2019 16:13:21 -0400 Subject: Draft JEP: Socket API for Remote Direct Memory Access (RDMA) In-Reply-To: <9ACD5B67AAC5594CB6268234CF29CF9AD1409AF5@ORSMSX113.amr.corp.intel.com> References: <9ACD5B67AAC5594CB6268234CF29CF9AD1409AF5@ORSMSX113.amr.corp.intel.com> Message-ID: Hi Lucy, Could you verify that documentation is not required for JEP 337: RDMA Network Sockets? I noticed that there's no JEP DOC task associated with it. If documentation is required, could you create a JEP DOC task for it? If documentation isn't required, could you add the docsnoimpact label to the JEP? Thanks, --Raymond On 2018-05-18 2:21 p.m., Lu, Yingqi wrote: > Hi All, > > We just submitted a JEP draft https://bugs.openjdk.java.net/browse/JDK-8203434. The proposal is to enhance the Java Socket API to support Remote Direct Memory Access (RDMA) using the rsocket protocol on the Linux-based platforms. > > Please review it and let us know your feedback. Thank you very much for your help! > > Thanks, > Lucy > > From: Lu, Yingqi > Sent: Friday, May 18, 2018 10:43 AM > To: 'jdk-dev at openjdk.java.net' > Cc: nio-dev at openjdk.java.net; Lu, Yingqi (yingqi.lu at intel.com) ; Kaczmarek, Eric ; Aundhe, Shirish ; Viswanathan, Sandhya ; 'Alan Bateman' ; 'Paul Sandoz' > Subject: Draft JEP: Socket API for Remote Direct Memory Access (RDMA) > > Hi All, > > Attached JEP draft is for bug 8195160 https://bugs.openjdk.java.net/browse/JDK-8195160. Please review it and let us know your feedback. This effort is to enhance the Java Socket API to support Remote Direct Memory Access (RDMA) using the rsocket protocol on the Linux-based platforms. > > Thank you for your help! > Lucy > > From forax at univ-mlv.fr Wed May 1 20:21:32 2019 From: forax at univ-mlv.fr (Remi Forax) Date: Wed, 1 May 2019 22:21:32 +0200 (CEST) Subject: Draft JEP: Keyword Management for the Java Language In-Reply-To: <5CC9F1E2.5040000@oracle.com> References: <5CC8ED67.6060008@oracle.com> <1092732121.508230.1556712431993.JavaMail.zimbra@u-pem.fr> <5CC9F1E2.5040000@oracle.com> Message-ID: <2055374928.541581.1556742092950.JavaMail.zimbra@u-pem.fr> ----- Mail original ----- > De: "Alex Buckley" > ?: "jdk-dev" > Envoy?: Mercredi 1 Mai 2019 21:22:10 > Objet: Re: Draft JEP: Keyword Management for the Java Language > Remi, thanks for your comments. > > On 5/1/2019 5:07 AM, Remi Forax wrote: >> - for the constraints on hyphenated keywords, using int-typed >> expressions is perhaps a little too clever because the compiler has >> to provide meaningful error message for the user (and IDEs automatic >> completion of not yet fully form expressions), by example, if there >> is an hyphenated keyword new-fun, for the snippet return A::new-fun, >> the expression is not valid but there are two interpretations A::new >> - fun or A:: new-fun. I think it's better to use a grammar approach >> (which keywords can be at left side or right side of an expression). >> Also the current rule doesn't work well if in the future we want to >> introduce operator overloading. > > I had some trouble understanding "using int-typed expressions is perhaps > a little too clever", because they're just examples to make a point, > while "a little too clever" is the kind of comment usually targeted at a > fundamental design decision. I think what you mean is "a little too > limiting". Thanks for reading my mind and not what i've written > To spell it all out: > > 1. Type-correct expressions that perform subtraction are part of the > "overlap" with hyphenated keywords; and > > 2. Type-incorrect statements that complete abruptly are part of the > overlap too (`throw-quickly` is syntactically valid today -- it will lex > and parse if `quickly` is a numeric variable -- but it is also > semantically invalid (type error), so we COULD reclassify it as a > hyphenated keyword, but we have ALREADY decided not to, per how `throw` > is mentioned in set A); and > > 3. [Remi's observation] Type-incorrect expressions that perform > subtraction are part of the overlap too (`A::new-fun` is syntactically > valid today, but semantically invalid, so we COULD reclassify it as a > hyphenated keyword, but we should be consistent with #2 and forbid > `new-*` hyphenated keywords like we do for `throw-*`). > > (You also raise the point that if the `-` operator could be overloaded, > then it might be semantically valid for the left operand to be a method > reference expression involving `::new`, and that would clash super-badly > with `new-*` hyphenated keywords.) I think 'this' are also missing from {A}, Foo.this is a valid expression (while semantically invalid). For 'null', 'true' and 'false', there are also valid expression but invalid semantically, so following the same logic they should be in {A} and {B}. in that case non-null is not a valid hyphenated keyword but it's a valid hyphenated keyword if contextual (as modifier for a field or a method). > > tl;dr I will add `new` to set A, and avoid so much focus there on > int-typed expressions. > >> - the example total-switch in section "hyphenated keywords" is >> invalid given the constraints you give. > > Oops! Removed. > > Alex regards, R?mi From yingqi.lu at intel.com Wed May 1 20:39:33 2019 From: yingqi.lu at intel.com (Lu, Yingqi) Date: Wed, 1 May 2019 20:39:33 +0000 Subject: Draft JEP: Socket API for Remote Direct Memory Access (RDMA) In-Reply-To: References: <9ACD5B67AAC5594CB6268234CF29CF9AD1409AF5@ORSMSX113.amr.corp.intel.com> Message-ID: <9ACD5B67AAC5594CB6268234CF29CF9AD16B17D0@ORSMSX113.amr.corp.intel.com> Hi Raymond, This is my first time doing JEP process. I am still learning it :-) I have JEP 337 available at https://openjdk.java.net/jeps/337 Is this the JEP DOC you refer to? If not, would you please provide a little more background/information on this so that I will create the subtask accordingly? Thank you very much for your help! Thanks, Lucy >-----Original Message----- >From: Raymond Gallardo [mailto:raymond.gallardo at oracle.com] >Sent: Wednesday, May 1, 2019 1:13 PM >To: Lu, Yingqi ; jdk-dev at openjdk.java.net >Cc: Aundhe, Shirish ; nio-dev at openjdk.java.net; >Kaczmarek, Eric >Subject: Re: Draft JEP: Socket API for Remote Direct Memory Access (RDMA) > >Hi Lucy, > >Could you verify that documentation is not required for JEP 337: RDMA >Network Sockets? I noticed that there's no JEP DOC task associated with it. > >If documentation is required, could you create a JEP DOC task for it? If >documentation isn't required, could you add the docsnoimpact label to the >JEP? > >Thanks, >--Raymond > >On 2018-05-18 2:21 p.m., Lu, Yingqi wrote: >> Hi All, >> >> We just submitted a JEP draft https://bugs.openjdk.java.net/browse/JDK- >8203434. The proposal is to enhance the Java Socket API to support Remote >Direct Memory Access (RDMA) using the rsocket protocol on the Linux-based >platforms. >> >> Please review it and let us know your feedback. Thank you very much for >your help! >> >> Thanks, >> Lucy >> >> From: Lu, Yingqi >> Sent: Friday, May 18, 2018 10:43 AM >> To: 'jdk-dev at openjdk.java.net' >> Cc: nio-dev at openjdk.java.net; Lu, Yingqi (yingqi.lu at intel.com) >> ; Kaczmarek, Eric ; >> Aundhe, Shirish ; Viswanathan, Sandhya >> ; 'Alan Bateman' >> ; 'Paul Sandoz' >> Subject: Draft JEP: Socket API for Remote Direct Memory Access (RDMA) >> >> Hi All, >> >> Attached JEP draft is for bug 8195160 >https://bugs.openjdk.java.net/browse/JDK-8195160. Please review it and let >us know your feedback. This effort is to enhance the Java Socket API to >support Remote Direct Memory Access (RDMA) using the rsocket protocol on >the Linux-based platforms. >> >> Thank you for your help! >> Lucy >> >> From alex.buckley at oracle.com Wed May 1 20:55:53 2019 From: alex.buckley at oracle.com (Alex Buckley) Date: Wed, 01 May 2019 13:55:53 -0700 Subject: Draft JEP: Keyword Management for the Java Language In-Reply-To: <2055374928.541581.1556742092950.JavaMail.zimbra@u-pem.fr> References: <5CC8ED67.6060008@oracle.com> <1092732121.508230.1556712431993.JavaMail.zimbra@u-pem.fr> <5CC9F1E2.5040000@oracle.com> <2055374928.541581.1556742092950.JavaMail.zimbra@u-pem.fr> Message-ID: <5CCA07D9.50100@oracle.com> On 5/1/2019 1:21 PM, Remi Forax wrote: > I think 'this' are also missing from {A}, Foo.this is a valid expression (while semantically invalid). Yes, and `Foo.this-day` is close enough to `Foo::new-day` that both can be explained together (so we don't forget why `this` ended up in set A). > For 'null', 'true' and 'false', there are also valid expression but invalid semantically, > so following the same logic they should be in {A} and {B}. > > in that case non-null is not a valid hyphenated keyword but it's a valid hyphenated keyword if contextual (as modifier for a field or a method). I think the JEP already takes reasonable care over `null`, `true`, and `false`. They're highlighted as literals rather than keywords early on, and `non-null` and `eventually-true` are clearly marked as examples of hyphenated _contextual_ keywords rather than hyphenated _classic_ keywords. Later, the "formal" statement involving sets A and B is specifically about hyphenated _classic_ keywords, so it doesn't advise on `non-null` at all. I could add constraints for hyphenated _contextual_ keywords but this JEP is a policy/approach, not a spec, so I'm going to stop here; this has been a productive thread. Alex From forax at univ-mlv.fr Wed May 1 21:23:39 2019 From: forax at univ-mlv.fr (Remi Forax) Date: Wed, 1 May 2019 23:23:39 +0200 (CEST) Subject: Draft JEP: Keyword Management for the Java Language In-Reply-To: <5CCA07D9.50100@oracle.com> References: <5CC8ED67.6060008@oracle.com> <1092732121.508230.1556712431993.JavaMail.zimbra@u-pem.fr> <5CC9F1E2.5040000@oracle.com> <2055374928.541581.1556742092950.JavaMail.zimbra@u-pem.fr> <5CCA07D9.50100@oracle.com> Message-ID: <1039144555.545854.1556745819891.JavaMail.zimbra@u-pem.fr> ----- Mail original ----- > De: "Alex Buckley" > ?: "jdk-dev" > Envoy?: Mercredi 1 Mai 2019 22:55:53 > Objet: Re: Draft JEP: Keyword Management for the Java Language > On 5/1/2019 1:21 PM, Remi Forax wrote: >> I think 'this' are also missing from {A}, Foo.this is a valid expression (while >> semantically invalid). > > Yes, and `Foo.this-day` is close enough to `Foo::new-day` that both can > be explained together (so we don't forget why `this` ended up in set A). > >> For 'null', 'true' and 'false', there are also valid expression but invalid >> semantically, >> so following the same logic they should be in {A} and {B}. >> >> in that case non-null is not a valid hyphenated keyword but it's a valid >> hyphenated keyword if contextual (as modifier for a field or a method). > > I think the JEP already takes reasonable care over `null`, `true`, and > `false`. They're highlighted as literals rather than keywords early on, > and `non-null` and `eventually-true` are clearly marked as examples of > hyphenated _contextual_ keywords rather than hyphenated _classic_ > keywords. Later, the "formal" statement involving sets A and B is > specifically about hyphenated _classic_ keywords, so it doesn't advise > on `non-null` at all. I could add constraints for hyphenated > _contextual_ keywords but this JEP is a policy/approach, not a spec, so > I'm going to stop here; this has been a productive thread. i agree. > > Alex R?mi From daniel.smith at oracle.com Fri May 3 23:44:16 2019 From: daniel.smith at oracle.com (Dan Smith) Date: Fri, 3 May 2019 17:44:16 -0600 Subject: Draft JEP: Keyword Management for the Java Language In-Reply-To: <5CC8ED67.6060008@oracle.com> References: <5CC8ED67.6060008@oracle.com> Message-ID: Clarification on the asides about `var`: "various linguistic heroics, such as reclassifying the identifier var as a type name but only in variable declarations" "a sequence of Java letters that is always tokenized as an identifier for which special provision is made in certain contexts (e.g., var, a type identifier in Java 10, also known as a reserved type name)." Here's the model: - `var` is an identifier - A *type identifier* is an identifier that can be used to name a type?a subset of all identifiers - `var` is *not* a type identifier - The identifier `var` is explicitly matched by the grammar rule LocalVariableType, and in that case given special meaning To supplement the discussion (and you've probably nodded in this direction enough already in the document), I'll note that I think there's still a lot of room for re-using the "type identifier" concept for certain keyword needs, such as modifiers. How I'd rephrase your notes: "various linguistic heroics, such as reclassifying the identifier var when it appears as a type name" "a sequence of Java letters that is always tokenized as an identifier for which special provision is made in certain contexts (e.g., var, a reserved type name in Java 10)." (I don't know if the term "reserved type name" is formally defined somewhere, but it seems like an appropriate description.) > On Apr 30, 2019, at 6:50 PM, Alex Buckley wrote: > > Evolving the Java language often means new keywords for new features, but new keywords risk breaking existing programs. In the Project Amber expert group, Brian Goetz suggested a technique for generating new keywords that balances compatibility and readability -- _hyphenated keywords_ -- and there is already a language feature raring to use it (JEP 354, Switch Expressions). > > We have now produced an Informational JEP to record the intent and detail of hyphenated keywords, for Feature JEPs may rely on. It also captures a policy for managing (that is, stewarding) Java's keywords more broadly. Your comments are welcome. > > https://bugs.openjdk.java.net/browse/JDK-8223002 > > Alex From alex.buckley at oracle.com Sat May 4 00:31:43 2019 From: alex.buckley at oracle.com (Alex Buckley) Date: Fri, 03 May 2019 17:31:43 -0700 Subject: Draft JEP: Keyword Management for the Java Language In-Reply-To: References: <5CC8ED67.6060008@oracle.com> Message-ID: <5CCCDD6F.1020007@oracle.com> On 5/3/2019 4:44 PM, Dan Smith wrote: > Clarification on the asides about `var`: > > "various linguistic heroics, such as reclassifying the identifier var as a type name but only in variable declarations" > > "a sequence of Java letters that is always tokenized as an identifier for which special provision is made in certain contexts (e.g., var, a type identifier in Java 10, also known as a reserved type name)." > > Here's the model: > - `var` is an identifier > - A *type identifier* is an identifier that can be used to name a type?a subset of all identifiers > - `var` is *not* a type identifier > - The identifier `var` is explicitly matched by the grammar rule LocalVariableType, and in that case given special meaning Oops, yes, the JEP was wrong to say "var, a type identifier in Java 10". > How I'd rephrase your notes: > > "various linguistic heroics, such as reclassifying the identifier var when it appears as a type name" The phrasing "such as X _but only in ..._, or Y _but only in ..._" is pedagogical -- it gets a point across in the high-level motivation. However, I agree that "reclassifying" is too strong for `var` -- it is always and everywhere an identifier -- so I have changed it to "such as treating the identifier `var` as a type name _but only in local variable declarations_" > "a sequence of Java letters that is always tokenized as an identifier for which special provision is made in certain contexts (e.g., var, a reserved type name in Java 10)." > > (I don't know if the term "reserved type name" is formally defined somewhere, but it seems like an appropriate description.) "reserved type name" isn't a JLS term, but I have no quarrel with it being the primary label for `var` in the JEP. I linked to the special syntactic treatment of `var` in 14.4 and the special semantic treatment in 14.4.1. Thanks, Alex From luke.hutch at gmail.com Mon May 6 23:57:29 2019 From: luke.hutch at gmail.com (Luke Hutchison) Date: Mon, 6 May 2019 17:57:29 -0600 Subject: Setting FILE_DISPOSITION_POSIX_SEMANTICS when deleting files on Windows Message-ID: Recent Windows 10 builds support POSIX-style file deletion semantics: https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/ntddk/ns-ntddk-_file_disposition_information_ex Setting this bit before deleting files using File::delete, Files::delete, Files::deleteIfExists etc. will work around the common problem on Windows where an attempt to delete an open file silently fails. This is a very common problem, experienced by developers when they forget to close not just any open OutputStream on a file before attempting to delete it, but also any open InputStream. This problem is exacerbated by the fact that a file cannot be deleted if it is mmap'd, and a file cannot be safely forcibly unmapped until it is garbage collected: https://bugs.openjdk.java.net/browse/JDK-4724038 Since file locking and deletion semantics are different on Windows than Linux and Mac OS X, and since the silent failure of file deletion when a file is open is almost always a source of surprise to developers coming from the Linux or Mac OS X world, the lack of default POSIX file deletion semantics on Windows presents a portability issue. I propose the FILE_DISPOSITION_POSIX_SEMANTICS bit be set for all delete operations in the Windows build of Java, to unify file deletion semantics across operating systems. From daniel.smith at oracle.com Tue May 7 02:01:46 2019 From: daniel.smith at oracle.com (Dan Smith) Date: Mon, 6 May 2019 20:01:46 -0600 Subject: Call for feedback -- switch expressions in JDK 12 In-Reply-To: References: <5CB688B0.7030502@oracle.com> <5CB767DD.3050503@oracle.com> <9472AED5-6D2A-4817-BE27-3D73FA9E6EA2@oracle.com> Message-ID: <66818050-FED2-4DEE-A6FD-8ED19A35D457@oracle.com> > On Apr 28, 2019, at 5:37 AM, Stephan Herrmann wrote: > > Other related concepts that don't exactly align with switch statement with ->: > - lambdas can be void compatible and/or value compatible. > This concept *could* be applied to switch also, but isn't. Lambda expressions have a unique problem: a particular lambda expression could be interpreted with respect to different target types, some of which have void returns and others of which have value returns. As an early way to characterize which sorts of target types it could be compatible with, we can identify a lambda body as value-compatible, void-compatible, or both. (Or neither, which is an error.) Method bodies don't have this problem: it's known up front whether a method is void or not, so we can proceed to check the body with that context firmly fixed. There's no such thing as a "void-compatible" method body. Switch statements/expressions are more like methods than like lambdas: we know based on enclosing syntax whether we're looking at a switch statement or a switch expression, so we can directly state rules about whether 'break-with' or 'break' should be used, and whether the block can complete normally. I don't think it would be useful to try to approach switch blocks in the same context-independent way we treat lambda bodies. > - we already have the concept of ExpressionStatement/StatementExpression, > for things that swing both ways, but switch does not participate in this, either. I think I noticed the rule is missing when reviewing the latest spec document, but the intent is: syntactically, a SwitchLabeledExpression is 'SwitchLabel -> Expression ;'. As an additional rule, in the context of a SwitchStatement, all the SwitchLabeledExpressions must be StatementExpressions. This is much the same way a lambda body with an expression form is checked for compatibility with a void return (15.12.2.1). Is that what you're referring to? From nielsbne at gmail.com Tue May 7 23:45:25 2019 From: nielsbne at gmail.com (Niels Bertram) Date: Wed, 8 May 2019 09:45:25 +1000 Subject: JDK packaged JAXP transformer indent no longer working in OpenJDK 11 Message-ID: Hi JDK devs, we recently started to upgrade from OpenJDK 8 to 11 and noticed that the Xalan transformer shipped with the JDK is not handling whitespace indentation properly anymore. Whilst it is not impacting the validity of the XML produced, it is rather annoying that indented results now have extra line breaks. E.g. we post-process some generated XSD files for publication but when done in OpenJDK 11 they look horrible. There are a few people seeing this issue: https://stackoverflow.com/questions/53596202/javax-xml-transform-transformer-line-endings-no-longer-respect-system-property https://github.com/CodeFX-org/java-9-wtf/tree/master/xml-transformer It may be related to the changes made in this ticket: https://bugs.openjdk.java.net/browse/JDK-8087303 Would it be possible for someone with permissions to raise a defect for this? $ java -version openjdk version "1.8.0_212" OpenJDK Runtime Environment (build 1.8.0_212-8u212-b01-1~deb9u1-b01) OpenJDK 64-Bit Server VM (build 25.212-b01, mixed mode) (sources at the end of mail) $ javac Transform.java $ java Transform test book $ java Transform --indent test book $ java -version openjdk version "11.0.3" 2019-04-16 OpenJDK Runtime Environment (build 11.0.3+1-Debian-1bpo91) OpenJDK 64-Bit Server VM (build 11.0.3+1-Debian-1bpo91, mixed mode, sharing) $ java Transform test book $ $ java -Djaxp.debug=1 Transform --indent JAXP: find factoryId =javax.xml.transform.TransformerFactory JAXP: loaded from fallback value: com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl JAXP: created new instance of class com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl using ClassLoader: null test book Source for Transform.java ------------------------------- import javax.xml.transform.OutputKeys; import javax.xml.transform.Templates; import javax.xml.transform.Transformer; import javax.xml.transform.TransformerFactory; import javax.xml.transform.stream.StreamResult; import javax.xml.transform.stream.StreamSource; import java.io.ByteArrayInputStream; import java.io.StringWriter; import java.nio.charset.StandardCharsets; public class Transform { public static void main(String[] args) { try { boolean indent = args != null && args.length == 1 && "--indent".equals(args[0]); String template = "\n" + " \n" + " \n" + " \n" + " \n" + " \n" + ""; String input = "\n" + " \n" + " test book\n" + " \n" + ""; Templates xsl = TransformerFactory.newInstance() .newTemplates(new StreamSource(new ByteArrayInputStream(template.getBytes(StandardCharsets.UTF_8)))); final StringWriter result = new StringWriter(); Transformer transformer = xsl.newTransformer(); // as soon as we configure auto-indent the output transformer.setOutputProperty(OutputKeys.INDENT, indent ? "yes" : "no"); transformer.transform(new StreamSource(new ByteArrayInputStream(input.getBytes(StandardCharsets.UTF_8))), new StreamResult(result)); System.out.println(result.toString()); } catch (Exception e) { e.printStackTrace(); } } } ------------------------------- From frank.yuan at oracle.com Wed May 8 06:21:24 2019 From: frank.yuan at oracle.com (Frank Yuan) Date: Wed, 8 May 2019 14:21:24 +0800 Subject: JDK packaged JAXP transformer indent no longer working in OpenJDK 11 In-Reply-To: References: Message-ID: <0feb01d50566$44dfd320$ce9f7960$@oracle.com> Hi Niels Yes, it's caused by JDK-8087303. But it's not a regression. This change has no impact to any xml parser at all, although it is not backward-compatible for the human readability, Actually JDK-8087303 tried to make the form better, but the serializer can't distinguish whether the space is a meaningful content or just an indentation made by the author, so we had to regard the spaces as xml data content. I think your program should not depend on any specified data format, so you have not any impact indeed, don't you? Thanks Frank > Subject: JDK packaged JAXP transformer indent no longer working in OpenJDK 11 > > Hi JDK devs, > > we recently started to upgrade from OpenJDK 8 to 11 and noticed that the > Xalan transformer shipped with the JDK is not handling whitespace > indentation properly anymore. Whilst it is not impacting the validity of > the XML produced, it is rather annoying that indented results now have > extra line breaks. E.g. we post-process some generated XSD files for > publication but when done in OpenJDK 11 they look horrible. > > There are a few people seeing this issue: > > https://stackoverflow.com/questions/53596202/javax-xml-transform-transformer-line-endings-no-longer-respect-system-property > This is not same as your issue. > https://github.com/CodeFX-org/java-9-wtf/tree/master/xml-transformer This talks about JDK-8087303. These changes were described in JDK 9 release notes. > > It may be related to the changes made in this ticket: > > https://bugs.openjdk.java.net/browse/JDK-8087303 > > Would it be possible for someone with permissions to raise a defect for > this? > > $ java -version > openjdk version "1.8.0_212" > OpenJDK Runtime Environment (build 1.8.0_212-8u212-b01-1~deb9u1-b01) > OpenJDK 64-Bit Server VM (build 25.212-b01, mixed mode) > > (sources at the end of mail) > > $ javac Transform.java > > $ java Transform > > > test book > > > > $ java Transform --indent > > > test book > > > > > $ java -version > openjdk version "11.0.3" 2019-04-16 > OpenJDK Runtime Environment (build 11.0.3+1-Debian-1bpo91) > OpenJDK 64-Bit Server VM (build 11.0.3+1-Debian-1bpo91, mixed mode, sharing) > > $ java Transform > > > test book > > > > $ $ java -Djaxp.debug=1 Transform --indent > JAXP: find factoryId =javax.xml.transform.TransformerFactory > JAXP: loaded from fallback value: > com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl > JAXP: created new instance of class > com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl using > ClassLoader: null > > > > > test book > > > > > > > Source for Transform.java > > ------------------------------- > > import javax.xml.transform.OutputKeys; > import javax.xml.transform.Templates; > import javax.xml.transform.Transformer; > import javax.xml.transform.TransformerFactory; > import javax.xml.transform.stream.StreamResult; > import javax.xml.transform.stream.StreamSource; > import java.io.ByteArrayInputStream; > import java.io.StringWriter; > import java.nio.charset.StandardCharsets; > > public class Transform { > > public static void main(String[] args) { > > try { > > boolean indent = args != null && args.length == 1 && > "--indent".equals(args[0]); > > String template = " http://www.w3.org/1999/XSL/Transform\">\n" + > " \n" + > " \n" + > " \n" + > " \n" + > " \n" + > ""; > > String input = "\n" + > " \n" + > " test book\n" + > " \n" + > ""; > > Templates xsl = TransformerFactory.newInstance() > .newTemplates(new StreamSource(new > ByteArrayInputStream(template.getBytes(StandardCharsets.UTF_8)))); > > final StringWriter result = new StringWriter(); > > Transformer transformer = xsl.newTransformer(); > > // as soon as we configure auto-indent the output > transformer.setOutputProperty(OutputKeys.INDENT, indent ? "yes" : > "no"); > > transformer.transform(new StreamSource(new > ByteArrayInputStream(input.getBytes(StandardCharsets.UTF_8))), new > StreamResult(result)); > > System.out.println(result.toString()); > } catch (Exception e) { > e.printStackTrace(); > } > > } > > } > ------------------------------- From nielsbne at gmail.com Wed May 8 13:44:11 2019 From: nielsbne at gmail.com (Niels Bertram) Date: Wed, 8 May 2019 23:44:11 +1000 Subject: JDK packaged JAXP transformer indent no longer working in OpenJDK 11 In-Reply-To: <0feb01d50566$44dfd320$ce9f7960$@oracle.com> References: <0feb01d50566$44dfd320$ce9f7960$@oracle.com> Message-ID: Hi Frank, the validity of the produced XML is not impaired. But given that we process and package the schema docs for humans, the readability is as important as validity. As a workaround, we have been able to rectify this issue by overriding the internal transformers with the official Xalan 2.7.2 ones. But given I am not the only one facing this issue, looks like a good case to evaluate if the changes applied in JDK-8087303 should be considered a regression. Certainly broke the the functionality we are used to when specifying indent=yes on the transformer factory. Cheers, Niels On Wed, May 8, 2019 at 4:23 PM Frank Yuan wrote: > Hi Niels > > Yes, it's caused by JDK-8087303. But it's not a regression. > > This change has no impact to any xml parser at all, although it is not > backward-compatible for the human readability, > > Actually JDK-8087303 tried to make the form better, but the serializer > can't distinguish whether the space is a meaningful content or just an > indentation made by the author, so we had to regard the spaces as xml data > content. > > I think your program should not depend on any specified data format, so > you have not any impact indeed, don't you? > > Thanks > Frank > > > Subject: JDK packaged JAXP transformer indent no longer working in > OpenJDK 11 > > > > Hi JDK devs, > > > > we recently started to upgrade from OpenJDK 8 to 11 and noticed that the > > Xalan transformer shipped with the JDK is not handling whitespace > > indentation properly anymore. Whilst it is not impacting the validity of > > the XML produced, it is rather annoying that indented results now have > > extra line breaks. E.g. we post-process some generated XSD files for > > publication but when done in OpenJDK 11 they look horrible. > > > > There are a few people seeing this issue: > > > > > https://stackoverflow.com/questions/53596202/javax-xml-transform-transformer-line-endings-no-longer-respect-system-property > > > This is not same as your issue. > > > https://github.com/CodeFX-org/java-9-wtf/tree/master/xml-transformer > This talks about JDK-8087303. These changes were described in JDK 9 > release notes. > > > > > It may be related to the changes made in this ticket: > > > > https://bugs.openjdk.java.net/browse/JDK-8087303 > > > > Would it be possible for someone with permissions to raise a defect for > > this? > > > > $ java -version > > openjdk version "1.8.0_212" > > OpenJDK Runtime Environment (build 1.8.0_212-8u212-b01-1~deb9u1-b01) > > OpenJDK 64-Bit Server VM (build 25.212-b01, mixed mode) > > > > (sources at the end of mail) > > > > $ javac Transform.java > > > > $ java Transform > > > > > > test book > > > > > > > > $ java Transform --indent > > > > > > test book > > > > > > > > > > $ java -version > > openjdk version "11.0.3" 2019-04-16 > > OpenJDK Runtime Environment (build 11.0.3+1-Debian-1bpo91) > > OpenJDK 64-Bit Server VM (build 11.0.3+1-Debian-1bpo91, mixed mode, > sharing) > > > > $ java Transform > > > > > > test book > > > > > > > > $ $ java -Djaxp.debug=1 Transform --indent > > JAXP: find factoryId =javax.xml.transform.TransformerFactory > > JAXP: loaded from fallback value: > > com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl > > JAXP: created new instance of class > > com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl using > > ClassLoader: null > > > > > > > > > > test book > > > > > > > > > > > > > > Source for Transform.java > > > > ------------------------------- > > > > import javax.xml.transform.OutputKeys; > > import javax.xml.transform.Templates; > > import javax.xml.transform.Transformer; > > import javax.xml.transform.TransformerFactory; > > import javax.xml.transform.stream.StreamResult; > > import javax.xml.transform.stream.StreamSource; > > import java.io.ByteArrayInputStream; > > import java.io.StringWriter; > > import java.nio.charset.StandardCharsets; > > > > public class Transform { > > > > public static void main(String[] args) { > > > > try { > > > > boolean indent = args != null && args.length == 1 && > > "--indent".equals(args[0]); > > > > String template = " > http://www.w3.org/1999/XSL/Transform\">\n" + > > " \n" + > > " \n" + > > " \n" + > > " \n" + > > " \n" + > > ""; > > > > String input = "\n" + > > " \n" + > > " test book\n" + > > " \n" + > > ""; > > > > Templates xsl = TransformerFactory.newInstance() > > .newTemplates(new StreamSource(new > > ByteArrayInputStream(template.getBytes(StandardCharsets.UTF_8)))); > > > > final StringWriter result = new StringWriter(); > > > > Transformer transformer = xsl.newTransformer(); > > > > // as soon as we configure auto-indent the output > > transformer.setOutputProperty(OutputKeys.INDENT, indent ? "yes" : > > "no"); > > > > transformer.transform(new StreamSource(new > > ByteArrayInputStream(input.getBytes(StandardCharsets.UTF_8))), new > > StreamResult(result)); > > > > System.out.println(result.toString()); > > } catch (Exception e) { > > e.printStackTrace(); > > } > > > > } > > > > } > > ------------------------------- > > From mark.reinhold at oracle.com Wed May 8 17:01:42 2019 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Wed, 08 May 2019 18:01:42 +0100 Subject: JEP proposed to target JDK 13: 350: Dynamic CDS Archives In-Reply-To: <20190425212613.B336F28837B@eggemoggin.niobe.net> References: <20190425212613.B336F28837B@eggemoggin.niobe.net> Message-ID: <20190508180142.662332370@eggemoggin.niobe.net> 2019/4/25 22:26:13 +0100, mark.reinhold at oracle.com: > The following JEP is proposed to target JDK 13: > > 350: Dynamic CDS Archives > https://openjdk.java.net/jeps/350 > > Feedback on this proposal from JDK Project Committers and Reviewers [1] > is more than welcome, as are reasoned objections. If no such objections > are raised by 23:00 UTC on Thursday, 2 May, or if they?re raised and > then satisfactorily answered, then per the JEP 2.0 process proposal [2] > I?ll target this JEP to JDK 13. Hearing no objections, I?ve targeted this JEP to JDK 13. - Mark From mark.reinhold at oracle.com Wed May 8 17:01:49 2019 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Wed, 08 May 2019 18:01:49 +0100 Subject: JEP proposed to target JDK 13: 351: ZGC: Uncommit Unused Memory In-Reply-To: <20190425212624.9B25F28837D@eggemoggin.niobe.net> References: <20190425212624.9B25F28837D@eggemoggin.niobe.net> Message-ID: <20190508180149.163384966@eggemoggin.niobe.net> 2019/4/25 22:26:24 +0100, mark.reinhold at oracle.com: > The following JEP is proposed to target JDK 13: > > 351: ZGC: Uncommit Unused Memory > https://openjdk.java.net/jeps/351 > > Feedback on this proposal from JDK Project Committers and Reviewers [1] > is more than welcome, as are reasoned objections. If no such objections > are raised by 23:00 UTC on Thursday, 2 May, or if they?re raised and > then satisfactorily answered, then per the JEP 2.0 process proposal [2] > I?ll target this JEP to JDK 13. Hearing no objections, I?ve targeted this JEP to JDK 13. - Mark From huizhe.wang at oracle.com Wed May 8 18:05:19 2019 From: huizhe.wang at oracle.com (Joe Wang) Date: Wed, 08 May 2019 11:05:19 -0700 Subject: JDK packaged JAXP transformer indent no longer working in OpenJDK 11 In-Reply-To: <0feb01d50566$44dfd320$ce9f7960$@oracle.com> References: <0feb01d50566$44dfd320$ce9f7960$@oracle.com> Message-ID: <5CD31A5F.4060507@oracle.com> Hi Frank, Can we improve on JDK-8087303 to not add the additional linebreak when auto-indent is set? This was probably brought up at the time. But it makes sense not to add linebreaks when there is already one. Thanks, Joe On 5/7/19, 11:21 PM, Frank Yuan wrote: > Hi Niels > > Yes, it's caused by JDK-8087303. But it's not a regression. > > This change has no impact to any xml parser at all, although it is not backward-compatible for the human readability, > > Actually JDK-8087303 tried to make the form better, but the serializer can't distinguish whether the space is a meaningful content or just an indentation made by the author, so we had to regard the spaces as xml data content. > > I think your program should not depend on any specified data format, so you have not any impact indeed, don't you? > > Thanks > Frank > >> Subject: JDK packaged JAXP transformer indent no longer working in OpenJDK 11 >> >> Hi JDK devs, >> >> we recently started to upgrade from OpenJDK 8 to 11 and noticed that the >> Xalan transformer shipped with the JDK is not handling whitespace >> indentation properly anymore. Whilst it is not impacting the validity of >> the XML produced, it is rather annoying that indented results now have >> extra line breaks. E.g. we post-process some generated XSD files for >> publication but when done in OpenJDK 11 they look horrible. >> >> There are a few people seeing this issue: >> >> https://stackoverflow.com/questions/53596202/javax-xml-transform-transformer-line-endings-no-longer-respect-system-property >> > This is not same as your issue. > >> https://github.com/CodeFX-org/java-9-wtf/tree/master/xml-transformer > This talks about JDK-8087303. These changes were described in JDK 9 release notes. > >> It may be related to the changes made in this ticket: >> >> https://bugs.openjdk.java.net/browse/JDK-8087303 >> >> Would it be possible for someone with permissions to raise a defect for >> this? >> >> $ java -version >> openjdk version "1.8.0_212" >> OpenJDK Runtime Environment (build 1.8.0_212-8u212-b01-1~deb9u1-b01) >> OpenJDK 64-Bit Server VM (build 25.212-b01, mixed mode) >> >> (sources at the end of mail) >> >> $ javac Transform.java >> >> $ java Transform >> >> >> test book >> >> >> >> $ java Transform --indent >> >> >> test book >> >> >> >> >> $ java -version >> openjdk version "11.0.3" 2019-04-16 >> OpenJDK Runtime Environment (build 11.0.3+1-Debian-1bpo91) >> OpenJDK 64-Bit Server VM (build 11.0.3+1-Debian-1bpo91, mixed mode, sharing) >> >> $ java Transform >> >> >> test book >> >> >> >> $ $ java -Djaxp.debug=1 Transform --indent >> JAXP: find factoryId =javax.xml.transform.TransformerFactory >> JAXP: loaded from fallback value: >> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl >> JAXP: created new instance of class >> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl using >> ClassLoader: null >> >> >> >> >> test book >> >> >> >> >> >> >> Source for Transform.java >> >> ------------------------------- >> >> import javax.xml.transform.OutputKeys; >> import javax.xml.transform.Templates; >> import javax.xml.transform.Transformer; >> import javax.xml.transform.TransformerFactory; >> import javax.xml.transform.stream.StreamResult; >> import javax.xml.transform.stream.StreamSource; >> import java.io.ByteArrayInputStream; >> import java.io.StringWriter; >> import java.nio.charset.StandardCharsets; >> >> public class Transform { >> >> public static void main(String[] args) { >> >> try { >> >> boolean indent = args != null&& args.length == 1&& >> "--indent".equals(args[0]); >> >> String template = "> http://www.w3.org/1999/XSL/Transform\">\n" + >> "\n" + >> "\n" + >> "\n" + >> "\n" + >> "\n" + >> ""; >> >> String input = "\n" + >> "\n" + >> "test book\n" + >> "\n" + >> ""; >> >> Templates xsl = TransformerFactory.newInstance() >> .newTemplates(new StreamSource(new >> ByteArrayInputStream(template.getBytes(StandardCharsets.UTF_8)))); >> >> final StringWriter result = new StringWriter(); >> >> Transformer transformer = xsl.newTransformer(); >> >> // as soon as we configure auto-indent the output >> transformer.setOutputProperty(OutputKeys.INDENT, indent ? "yes" : >> "no"); >> >> transformer.transform(new StreamSource(new >> ByteArrayInputStream(input.getBytes(StandardCharsets.UTF_8))), new >> StreamResult(result)); >> >> System.out.println(result.toString()); >> } catch (Exception e) { >> e.printStackTrace(); >> } >> >> } >> >> } >> ------------------------------- From volker.simonis at gmail.com Thu May 9 08:07:48 2019 From: volker.simonis at gmail.com (Volker Simonis) Date: Thu, 9 May 2019 10:07:48 +0200 Subject: CFV: New JDK Reviewer: Matthias Baesken Message-ID: I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. Matthias is a long standing member of the JVM team at SAP. He's main areas of expertise are the build system, compilers/porting and security updates. He's a JDK Committer who has contributed more than 90 changes within the last two years [1]. Votes are due by 23 May 2019, 12:00 CET. Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. For Three-Vote Consensus voting instructions, see [3]. Volker Simonis [1] http://hg.openjdk.java.net/jdk/jdk/search/?rev=((author(%22mbaesken%22)%20and%20not%20desc(%22Contributed-by%22))%20or%20desc(%22Contributed-by%3A%20matthias.baesken%40sap.com%22))%20and%20not%20merge()&revcount=100 [2] http://openjdk.java.net/census [3] http://openjdk.java.net/projects/#reviewer-vote From shade at redhat.com Thu May 9 08:10:16 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Thu, 9 May 2019 10:10:16 +0200 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: <87c9188e-46ce-3ee9-b88a-8a2195918fac@redhat.com> Vote: yes On 5/9/19 10:07 AM, Volker Simonis wrote: > I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. From goetz.lindenmaier at sap.com Thu May 9 08:13:25 2019 From: goetz.lindenmaier at sap.com (Lindenmaier, Goetz) Date: Thu, 9 May 2019 08:13:25 +0000 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: vote: yes Best regards, Goetz. > -----Original Message----- > From: jdk-dev On Behalf Of Volker > Simonis > Sent: Donnerstag, 9. Mai 2019 10:08 > To: jdk-dev > Subject: CFV: New JDK Reviewer: Matthias Baesken > > I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. > > Matthias is a long standing member of the JVM team at SAP. He's main > areas of expertise are the build system, compilers/porting and > security updates. He's a JDK Committer who has contributed more than > 90 changes within the last two years [1]. > > Votes are due by 23 May 2019, 12:00 CET. > > Only current JDK Reviewers [2] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this > mailing list. > > For Three-Vote Consensus voting instructions, see [3]. > > Volker Simonis > > [1] > http://hg.openjdk.java.net/jdk/jdk/search/?rev=((author(%22mbaesken%22)% > 20and%20not%20desc(%22Contributed- > by%22))%20or%20desc(%22Contributed- > by%3A%20matthias.baesken%40sap.com%22))%20and%20not%20merge()&re > vcount=100 > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#reviewer-vote From ivan.gerasimov at oracle.com Thu May 9 08:26:36 2019 From: ivan.gerasimov at oracle.com (Ivan Gerasimov) Date: Thu, 9 May 2019 01:26:36 -0700 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: <4669ff57-3115-558f-15f0-969dd27ecd6c@oracle.com> Vote: Yes On 5/9/19 1:07 AM, Volker Simonis wrote: > I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. -- With kind regards, Ivan Gerasimov From francois.farquet at oracle.com Thu May 9 08:32:44 2019 From: francois.farquet at oracle.com (Francois Farquet) Date: Thu, 9 May 2019 10:32:44 +0200 Subject: Announcing the Renaissance benchmark suite Message-ID: <1d69224f-c58f-2248-5312-95b8a9b19167@oracle.com> Dear all, We are pleased to announce the release of the Renaissance Benchmark Suite. This new suite is intended to provide workloads that are not available elsewhere, and thus complement the workloads found in the existing, commonly used benchmark suites for the JVM, such as DaCapo, ScalaBench, and SPECjvm2008, which we gratefully acknowledge. We have found a great deal of inspiration in these suites, and strive to match and, where possible, exceed, the level of quality and usability established by these suites. We aim to make the Renaissance development process as open as possible, and invite the community to participate. The code is open-source and the contribution mechanism is open. The suite will be regularly updated through minor releases, while new benchmarks will be introduced or retired in major releases. Version 0.9 marks the first public open-source release of the Renaissance suite and is considered a major release candidate with respect to the selection of workloads included in the suite. We are still stabilizing the internal design until the 1.0 major release which should be ready in a few weeks. In the meantime, any feedback or contribution is very welcome. Repository : https://github.com/renaissance-benchmarks/renaissance/ Website : https://renaissance.dev/ Thanks, Francois Farquet From martin.doerr at sap.com Thu May 9 09:17:38 2019 From: martin.doerr at sap.com (Doerr, Martin) Date: Thu, 9 May 2019 09:17:38 +0000 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: <87c9188e-46ce-3ee9-b88a-8a2195918fac@redhat.com> References: <87c9188e-46ce-3ee9-b88a-8a2195918fac@redhat.com> Message-ID: Vote: yes Best regards, Martin From christoph.langer at sap.com Thu May 9 09:59:30 2019 From: christoph.langer at sap.com (Langer, Christoph) Date: Thu, 9 May 2019 09:59:30 +0000 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: Vote:yes > -----Original Message----- > From: jdk-dev On Behalf Of Volker > Simonis > Sent: Donnerstag, 9. Mai 2019 10:08 > To: jdk-dev > Subject: CFV: New JDK Reviewer: Matthias Baesken > > I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. > > Matthias is a long standing member of the JVM team at SAP. He's main > areas of expertise are the build system, compilers/porting and > security updates. He's a JDK Committer who has contributed more than > 90 changes within the last two years [1]. > > Votes are due by 23 May 2019, 12:00 CET. > > Only current JDK Reviewers [2] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this > mailing list. > > For Three-Vote Consensus voting instructions, see [3]. > > Volker Simonis > > [1] > http://hg.openjdk.java.net/jdk/jdk/search/?rev=((author(%22mbaesken%2 > 2)%20and%20not%20desc(%22Contributed- > by%22))%20or%20desc(%22Contributed- > by%3A%20matthias.baesken%40sap.com%22))%20and%20not%20merge()& > revcount=100 > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#reviewer-vote From coleen.phillimore at oracle.com Thu May 9 11:38:42 2019 From: coleen.phillimore at oracle.com (coleen.phillimore at oracle.com) Date: Thu, 9 May 2019 07:38:42 -0400 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: <4de9b6fc-db89-a6dc-2348-499505f9212e@oracle.com> Vote: yes On 5/9/19 4:07 AM, Volker Simonis wrote: > I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. > > Matthias is a long standing member of the JVM team at SAP. He's main > areas of expertise are the build system, compilers/porting and > security updates. He's a JDK Committer who has contributed more than > 90 changes within the last two years [1]. > > Votes are due by 23 May 2019, 12:00 CET. > > Only current JDK Reviewers [2] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this > mailing list. > > For Three-Vote Consensus voting instructions, see [3]. > > Volker Simonis > > [1] http://hg.openjdk.java.net/jdk/jdk/search/?rev=((author(%22mbaesken%22)%20and%20not%20desc(%22Contributed-by%22))%20or%20desc(%22Contributed-by%3A%20matthias.baesken%40sap.com%22))%20and%20not%20merge()&revcount=100 > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#reviewer-vote From lois.foltan at oracle.com Thu May 9 11:39:40 2019 From: lois.foltan at oracle.com (Lois Foltan) Date: Thu, 9 May 2019 07:39:40 -0400 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: <65f87501-c65d-a73c-620c-afa1cadf8203@oracle.com> Vote: yes On 5/9/2019 4:07 AM, Volker Simonis wrote: > I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. > > Matthias is a long standing member of the JVM team at SAP. He's main > areas of expertise are the build system, compilers/porting and > security updates. He's a JDK Committer who has contributed more than > 90 changes within the last two years [1]. > > Votes are due by 23 May 2019, 12:00 CET. > > Only current JDK Reviewers [2] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this > mailing list. > > For Three-Vote Consensus voting instructions, see [3]. > > Volker Simonis > > [1] http://hg.openjdk.java.net/jdk/jdk/search/?rev=((author(%22mbaesken%22)%20and%20not%20desc(%22Contributed-by%22))%20or%20desc(%22Contributed-by%3A%20matthias.baesken%40sap.com%22))%20and%20not%20merge()&revcount=100 > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#reviewer-vote From harold.seigel at oracle.com Thu May 9 12:17:07 2019 From: harold.seigel at oracle.com (Harold Seigel) Date: Thu, 9 May 2019 08:17:07 -0400 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: Vote: yes Harold On 5/9/2019 4:07 AM, Volker Simonis wrote: > I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. > > Matthias is a long standing member of the JVM team at SAP. He's main > areas of expertise are the build system, compilers/porting and > security updates. He's a JDK Committer who has contributed more than > 90 changes within the last two years [1]. > > Votes are due by 23 May 2019, 12:00 CET. > > Only current JDK Reviewers [2] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this > mailing list. > > For Three-Vote Consensus voting instructions, see [3]. > > Volker Simonis > > [1] http://hg.openjdk.java.net/jdk/jdk/search/?rev=((author(%22mbaesken%22)%20and%20not%20desc(%22Contributed-by%22))%20or%20desc(%22Contributed-by%3A%20matthias.baesken%40sap.com%22))%20and%20not%20merge()&revcount=100 > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#reviewer-vote From kim.barrett at oracle.com Thu May 9 14:11:46 2019 From: kim.barrett at oracle.com (Kim Barrett) Date: Thu, 9 May 2019 10:11:46 -0400 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: vote: yes > On May 9, 2019, at 4:07 AM, Volker Simonis wrote: > > I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. > > Matthias is a long standing member of the JVM team at SAP. He's main > areas of expertise are the build system, compilers/porting and > security updates. He's a JDK Committer who has contributed more than > 90 changes within the last two years [1]. > > Votes are due by 23 May 2019, 12:00 CET. > > Only current JDK Reviewers [2] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this > mailing list. > > For Three-Vote Consensus voting instructions, see [3]. > > Volker Simonis > > [1] http://hg.openjdk.java.net/jdk/jdk/search/?rev=((author(%22mbaesken%22)%20and%20not%20desc(%22Contributed-by%22))%20or%20desc(%22Contributed-by%3A%20matthias.baesken%40sap.com%22))%20and%20not%20merge()&revcount=100 > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#reviewer-vote From jianglizhou at google.com Thu May 9 14:49:13 2019 From: jianglizhou at google.com (Jiangli Zhou) Date: Thu, 9 May 2019 07:49:13 -0700 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: Vote: Yes Best Regards, Jiangli From: Volker Simonis Date: Thu, May 9, 2019 at 1:08 AM To: jdk-dev > I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. > > Matthias is a long standing member of the JVM team at SAP. He's main > areas of expertise are the build system, compilers/porting and > security updates. He's a JDK Committer who has contributed more than > 90 changes within the last two years [1]. > > Votes are due by 23 May 2019, 12:00 CET. > > Only current JDK Reviewers [2] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this > mailing list. > > For Three-Vote Consensus voting instructions, see [3]. > > Volker Simonis > > [1] http://hg.openjdk.java.net/jdk/jdk/search/?rev=((author(%22mbaesken%22)%20and%20not%20desc(%22Contributed-by%22))%20or%20desc(%22Contributed-by%3A%20matthias.baesken%40sap.com%22))%20and%20not%20merge()&revcount=100 > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#reviewer-vote From vladimir.kozlov at oracle.com Thu May 9 14:51:37 2019 From: vladimir.kozlov at oracle.com (Vladimir Kozlov) Date: Thu, 9 May 2019 07:51:37 -0700 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: Vote yes Thanks Vladimir > On May 9, 2019, at 7:49 AM, Jiangli Zhou wrote: > > Vote: Yes > > Best Regards, > Jiangli > > From: Volker Simonis > Date: Thu, May 9, 2019 at 1:08 AM > To: jdk-dev > >> I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. >> >> Matthias is a long standing member of the JVM team at SAP. He's main >> areas of expertise are the build system, compilers/porting and >> security updates. He's a JDK Committer who has contributed more than >> 90 changes within the last two years [1]. >> >> Votes are due by 23 May 2019, 12:00 CET. >> >> Only current JDK Reviewers [2] are eligible to vote on this >> nomination. Votes must be cast in the open by replying to this >> mailing list. >> >> For Three-Vote Consensus voting instructions, see [3]. >> >> Volker Simonis >> >> [1] http://hg.openjdk.java.net/jdk/jdk/search/?rev=((author(%22mbaesken%22)%20and%20not%20desc(%22Contributed-by%22))%20or%20desc(%22Contributed-by%3A%20matthias.baesken%40sap.com%22))%20and%20not%20merge()&revcount=100 >> [2] http://openjdk.java.net/census >> [3] http://openjdk.java.net/projects/#reviewer-vote From Alan.Bateman at oracle.com Thu May 9 17:02:06 2019 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Thu, 9 May 2019 18:02:06 +0100 Subject: Announcing the Renaissance benchmark suite In-Reply-To: <1d69224f-c58f-2248-5312-95b8a9b19167@oracle.com> References: <1d69224f-c58f-2248-5312-95b8a9b19167@oracle.com> Message-ID: <0c6f0406-35c7-425a-49fe-e0b4bbcd579e@oracle.com> On 09/05/2019 09:32, Francois Farquet wrote: > Dear all, > > We are pleased to announce the release of the Renaissance Benchmark > Suite. This new suite is intended to provide workloads that are not > available elsewhere, and thus complement the workloads found in the > existing, commonly used benchmark suites for the JVM, such as DaCapo, > ScalaBench, and SPECjvm2008, which we gratefully acknowledge. We have > found a great deal of inspiration in these suites, and strive to match > and, where possible, exceed, the level of quality and usability > established by these suites. > > We aim to make the Renaissance development process as open as > possible, and invite the community to participate. The code is > open-source and the contribution mechanism is open. The suite will be > regularly updated through minor releases, while new benchmarks will be > introduced or retired in major releases. > > Version 0.9 marks the first public open-source release of the > Renaissance suite and is considered a major release candidate with > respect to the selection of workloads included in the suite. We are > still stabilizing the internal design until the 1.0 major release > which should be ready in a few weeks. In the meantime, any feedback or > contribution is very welcome. > > Repository : https://github.com/renaissance-benchmarks/renaissance/ > Website : https://renaissance.dev/ > This looks very interesting. I followed the link to the CI and see it's built/run on 8, 9, and 11. Are all benchmarks runnable on the main line, as in jdk/jdk or the current JDK 13 EA builds? Is there anyone lined up to have it run on a regularly basis with current platforms and configurations? -Alan From francois.farquet at oracle.com Thu May 9 18:04:35 2019 From: francois.farquet at oracle.com (Francois Farquet) Date: Thu, 9 May 2019 18:04:35 +0000 (UTC) Subject: Announcing the Renaissance benchmark suite In-Reply-To: <0c6f0406-35c7-425a-49fe-e0b4bbcd579e@oracle.com> References: <1d69224f-c58f-2248-5312-95b8a9b19167@oracle.com> <0c6f0406-35c7-425a-49fe-e0b4bbcd579e@oracle.com> Message-ID: <2F21ACDC37E6D290.0D834AD5-A9BB-4012-80F0-2DF248C956F1@mail.outlook.com> Hi Alan, The suite has been developed and tested under JDK8 and full support of JDK11 is planned for the 1.0.0 release.Regarding the latest JDK and ea versions, we?ll do our best to test it regularly but if the Java Product Group at Oracle could regularly check its compatibility and performance, that would be great. Thanks, - Francois On Thu, May 9, 2019 at 7:03 PM +0200, "Alan Bateman" wrote: On 09/05/2019 09:32, Francois Farquet wrote: > Dear all, > > We are pleased to announce the release of the Renaissance Benchmark > Suite. This new suite is intended to provide workloads that are not > available elsewhere, and thus complement the workloads found in the > existing, commonly used benchmark suites for the JVM, such as DaCapo, > ScalaBench, and SPECjvm2008, which we gratefully acknowledge. We have > found a great deal of inspiration in these suites, and strive to match > and, where possible, exceed, the level of quality and usability > established by these suites. > > We aim to make the Renaissance development process as open as > possible, and invite the community to participate. The code is > open-source and the contribution mechanism is open. The suite will be > regularly updated through minor releases, while new benchmarks will be > introduced or retired in major releases. > > Version 0.9 marks the first public open-source release of the > Renaissance suite and is considered a major release candidate with > respect to the selection of workloads included in the suite. We are > still stabilizing the internal design until the 1.0 major release > which should be ready in a few weeks. In the meantime, any feedback or > contribution is very welcome. > > Repository : https://github.com/renaissance-benchmarks/renaissance/ > Website : https://renaissance.dev/ > This looks very interesting. I followed the link to the CI and see it's built/run on 8, 9, and 11. Are all benchmarks runnable on the main line, as in jdk/jdk or the current JDK 13 EA builds? Is there anyone lined up to have it run on a regularly basis with current platforms and configurations? -Alan From serguei.spitsyn at oracle.com Thu May 9 20:11:17 2019 From: serguei.spitsyn at oracle.com (serguei.spitsyn at oracle.com) Date: Thu, 9 May 2019 13:11:17 -0700 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: Vote: yes From vladimir.x.ivanov at oracle.com Thu May 9 20:16:03 2019 From: vladimir.x.ivanov at oracle.com (Vladimir Ivanov) Date: Thu, 9 May 2019 13:16:03 -0700 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: Vote: yes Best regards, Vladimir Ivanov On 09/05/2019 01:07, Volker Simonis wrote: > I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. From david.holmes at oracle.com Thu May 9 22:18:55 2019 From: david.holmes at oracle.com (David Holmes) Date: Fri, 10 May 2019 08:18:55 +1000 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: Vote: yes David On 9/05/2019 6:07 pm, Volker Simonis wrote: > I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. > > Matthias is a long standing member of the JVM team at SAP. He's main > areas of expertise are the build system, compilers/porting and > security updates. He's a JDK Committer who has contributed more than > 90 changes within the last two years [1]. > > Votes are due by 23 May 2019, 12:00 CET. > > Only current JDK Reviewers [2] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this > mailing list. > > For Three-Vote Consensus voting instructions, see [3]. > > Volker Simonis > > [1] http://hg.openjdk.java.net/jdk/jdk/search/?rev=((author(%22mbaesken%22)%20and%20not%20desc(%22Contributed-by%22))%20or%20desc(%22Contributed-by%3A%20matthias.baesken%40sap.com%22))%20and%20not%20merge()&revcount=100 > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#reviewer-vote > From christoph.langer at sap.com Fri May 10 07:51:50 2019 From: christoph.langer at sap.com (Langer, Christoph) Date: Fri, 10 May 2019 07:51:50 +0000 Subject: CFV: New JDK Committer: Ralf Schmelter Message-ID: I hereby nominate Ralf Schmelter (rschmelter) to JDK Project Committer. Ralf is a long term member of the SAP JVM team with experience in various areas such as hotspot, garbage collection, debugging/JVMTI and many more. He started contributing to OpenJDK quite recently and has already piled up 13 changesets [3]. I think it's about time to make him a Committer. Votes are due by May 24 12:00 CET. Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. For Lazy Consensus voting instructions, see [2]. Christoph Langer [1] http://openjdk.java.net/census [2] http://openjdk.java.net/projects/#committer-vote [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22rschmelter%22%29%20or%20desc%28%22Contributed-by%3A%20ralf.schmelter%40sap.com%22%29%29%20and%20not%20merge%28%29&revcount=40 From volker.simonis at gmail.com Fri May 10 07:55:20 2019 From: volker.simonis at gmail.com (Volker Simonis) Date: Fri, 10 May 2019 09:55:20 +0200 Subject: CFV: New JDK Committer: Ralf Schmelter In-Reply-To: References: Message-ID: Vote: yes Best regards, Volker On Fri, May 10, 2019 at 9:52 AM Langer, Christoph wrote: > > I hereby nominate Ralf Schmelter (rschmelter) to JDK Project Committer. > > Ralf is a long term member of the SAP JVM team with experience in various areas such as hotspot, garbage collection, debugging/JVMTI and many more. > > He started contributing to OpenJDK quite recently and has already piled up 13 changesets [3]. I think it's about time to make him a Committer. > > Votes are due by May 24 12:00 CET. > > Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22rschmelter%22%29%20or%20desc%28%22Contributed-by%3A%20ralf.schmelter%40sap.com%22%29%29%20and%20not%20merge%28%29&revcount=40 > From goetz.lindenmaier at sap.com Fri May 10 07:58:57 2019 From: goetz.lindenmaier at sap.com (Lindenmaier, Goetz) Date: Fri, 10 May 2019 07:58:57 +0000 Subject: CFV: New JDK Committer: Ralf Schmelter In-Reply-To: References: Message-ID: Vote: yes Best regards, Goetz. > -----Original Message----- > From: jdk-dev On Behalf Of Langer, > Christoph > Sent: Friday, May 10, 2019 9:52 AM > To: jdk-dev > Cc: Schmelter, Ralf > Subject: [CAUTION] CFV: New JDK Committer: Ralf Schmelter > > I hereby nominate Ralf Schmelter (rschmelter) to JDK Project Committer. > > Ralf is a long term member of the SAP JVM team with experience in various > areas such as hotspot, garbage collection, debugging/JVMTI and many more. > > He started contributing to OpenJDK quite recently and has already piled up > 13 changesets [3]. I think it's about time to make him a Committer. > > Votes are due by May 24 12:00 CET. > > Only current JDK Committers [1] are eligible to vote on this nomination. > Votes must be cast in the open by replying to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] > http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22rschmel > ter%22%29%20or%20desc%28%22Contributed- > by%3A%20ralf.schmelter%40sap.com%22%29%29%20and%20not%20merge > %28%29&revcount=40 From sgehwolf at redhat.com Fri May 10 08:03:55 2019 From: sgehwolf at redhat.com (sgehwolf at redhat.com) Date: Fri, 10 May 2019 10:03:55 +0200 Subject: CFV: New JDK Committer: Ralf Schmelter In-Reply-To: References: Message-ID: <238e75209ed437c39a1e806f9dd89500817b96ab.camel@redhat.com> Vote: yes On Fri, 2019-05-10 at 07:51 +0000, Langer, Christoph wrote: > I hereby nominate Ralf Schmelter (rschmelter) to JDK Project > Committer. From martin.doerr at sap.com Fri May 10 08:10:20 2019 From: martin.doerr at sap.com (Doerr, Martin) Date: Fri, 10 May 2019 08:10:20 +0000 Subject: CFV: New JDK Committer: Ralf Schmelter In-Reply-To: References: Message-ID: Vote: yes Best regards, Martin From fujie at loongson.cn Fri May 10 09:23:35 2019 From: fujie at loongson.cn (Jie Fu) Date: Fri, 10 May 2019 17:23:35 +0800 Subject: Announcing the Renaissance benchmark suite In-Reply-To: <1d69224f-c58f-2248-5312-95b8a9b19167@oracle.com> References: <1d69224f-c58f-2248-5312-95b8a9b19167@oracle.com> Message-ID: <1d8cfd4e-b679-cf6b-d18b-bc20123258d4@loongson.cn> Hi Francois, Very cool! Thanks. Is there a mailing list about Renaissance? The website could be more perfect if the following issues be fixed: ?1) "target/scala-2.12" might be "target/renaissance-0.9.0.jar" on page[1] under "Building the suite". ?2) The page link[2], which was referenced in[1] under "Contributing", was not found there. Best regards, Jie [1] https://renaissance.dev/docs [2] https://renaissance.dev/CONTRIBUTION.md On 2019/5/9 ??4:32, Francois Farquet wrote: > Dear all, > > We are pleased to announce the release of the Renaissance Benchmark > Suite. This new suite is intended to provide workloads that are not > available elsewhere, and thus complement the workloads found in the > existing, commonly used benchmark suites for the JVM, such as DaCapo, > ScalaBench, and SPECjvm2008, which we gratefully acknowledge. We have > found a great deal of inspiration in these suites, and strive to match > and, where possible, exceed, the level of quality and usability > established by these suites. > > We aim to make the Renaissance development process as open as > possible, and invite the community to participate. The code is > open-source and the contribution mechanism is open. The suite will be > regularly updated through minor releases, while new benchmarks will be > introduced or retired in major releases. > > Version 0.9 marks the first public open-source release of the > Renaissance suite and is considered a major release candidate with > respect to the selection of workloads included in the suite. We are > still stabilizing the internal design until the 1.0 major release > which should be ready in a few weeks. In the meantime, any feedback or > contribution is very welcome. > > Repository : https://github.com/renaissance-benchmarks/renaissance/ > Website : https://renaissance.dev/ > > Thanks, > > Francois Farquet > > From francois.farquet at oracle.com Fri May 10 11:33:27 2019 From: francois.farquet at oracle.com (Francois Farquet) Date: Fri, 10 May 2019 13:33:27 +0200 Subject: Announcing the Renaissance benchmark suite In-Reply-To: <1d8cfd4e-b679-cf6b-d18b-bc20123258d4@loongson.cn> References: <1d69224f-c58f-2248-5312-95b8a9b19167@oracle.com> <1d8cfd4e-b679-cf6b-d18b-bc20123258d4@loongson.cn> Message-ID: <8dd949e7-4f40-a7e1-efc7-eddaecf0d0fa@oracle.com> Hi Jie, Yes, we have a Google group here : https://groups.google.com/forum/#!forum/renaissance-dev And a Twitter account (@RenaissanceJVM) : https://twitter.com/renaissancejvm Thanks for the report about the website problems, we will fix that shortly. Bests, Francois Le 10.05.19 ? 11:23, Jie Fu a ?crit?: > Hi Francois, > > Very cool! Thanks. > > Is there a mailing list about Renaissance? > > The website could be more perfect if the following issues be fixed: > ?1) "target/scala-2.12" might be "target/renaissance-0.9.0.jar" on > page[1] under "Building the suite". > ?2) The page link[2], which was referenced in[1] under "Contributing", > was not found there. > > Best regards, > Jie > > [1] > https://urldefense.proofpoint.com/v2/url?u=https-3A__renaissance.dev_docs&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=A2eR84h9-mSFlGoC541LbA5ml9kGSBgXjBrlPh1tAlI&m=BmnULNn2SK9LEu1bd9fRDxZ6dJgfjEA4OtN8SjwKspI&s=2srmNs2vWiED4YXPKG4WpgSHU60NYiSBy91XRatPTzQ&e= > [2] > https://urldefense.proofpoint.com/v2/url?u=https-3A__renaissance.dev_CONTRIBUTION.md&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=A2eR84h9-mSFlGoC541LbA5ml9kGSBgXjBrlPh1tAlI&m=BmnULNn2SK9LEu1bd9fRDxZ6dJgfjEA4OtN8SjwKspI&s=p4g7Zqt4xc9mHHsTl-vVSGLBLXlIGPlBF9fjVxMHtHc&e= > > > On 2019/5/9 ??4:32, Francois Farquet wrote: >> Dear all, >> >> We are pleased to announce the release of the Renaissance Benchmark >> Suite. This new suite is intended to provide workloads that are not >> available elsewhere, and thus complement the workloads found in the >> existing, commonly used benchmark suites for the JVM, such as DaCapo, >> ScalaBench, and SPECjvm2008, which we gratefully acknowledge. We have >> found a great deal of inspiration in these suites, and strive to >> match and, where possible, exceed, the level of quality and usability >> established by these suites. >> >> We aim to make the Renaissance development process as open as >> possible, and invite the community to participate. The code is >> open-source and the contribution mechanism is open. The suite will be >> regularly updated through minor releases, while new benchmarks will >> be introduced or retired in major releases. >> >> Version 0.9 marks the first public open-source release of the >> Renaissance suite and is considered a major release candidate with >> respect to the selection of workloads included in the suite. We are >> still stabilizing the internal design until the 1.0 major release >> which should be ready in a few weeks. In the meantime, any feedback >> or contribution is very welcome. >> >> Repository : >> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_renaissance-2Dbenchmarks_renaissance_&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=A2eR84h9-mSFlGoC541LbA5ml9kGSBgXjBrlPh1tAlI&m=BmnULNn2SK9LEu1bd9fRDxZ6dJgfjEA4OtN8SjwKspI&s=kLdoHZOI1qQH9SbwjL52xFV4PkrkF28eWnd6kAQn12A&e= >> Website : >> https://urldefense.proofpoint.com/v2/url?u=https-3A__renaissance.dev_&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=A2eR84h9-mSFlGoC541LbA5ml9kGSBgXjBrlPh1tAlI&m=BmnULNn2SK9LEu1bd9fRDxZ6dJgfjEA4OtN8SjwKspI&s=ObnqyI-MrdN6EtjHZQt8-3BTC4fIrh6m-vTVpeAljZo&e= >> >> Thanks, >> >> Francois Farquet >> >> > From Alan.Bateman at oracle.com Fri May 10 12:39:35 2019 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Fri, 10 May 2019 13:39:35 +0100 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: <1b85f248-2f4e-5ec5-136e-7ba10fbf5bac@oracle.com> Vote: yes From thomas.stuefe at gmail.com Fri May 10 13:27:40 2019 From: thomas.stuefe at gmail.com (=?UTF-8?Q?Thomas_St=C3=BCfe?=) Date: Fri, 10 May 2019 15:27:40 +0200 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: <1b85f248-2f4e-5ec5-136e-7ba10fbf5bac@oracle.com> References: <1b85f248-2f4e-5ec5-136e-7ba10fbf5bac@oracle.com> Message-ID: Vote: yes On Fri, May 10, 2019, 2:43 PM Alan Bateman wrote: > Vote: yes > From vladimir.kozlov at oracle.com Fri May 10 16:08:09 2019 From: vladimir.kozlov at oracle.com (Vladimir Kozlov) Date: Fri, 10 May 2019 09:08:09 -0700 Subject: CFV: New JDK Committer: Ralf Schmelter In-Reply-To: References: Message-ID: <569081BB-4334-43FE-9923-FBD1EAAA89BA@oracle.com> Vote yes Thanks Vladimir > On May 10, 2019, at 12:51 AM, Langer, Christoph wrote: > > I hereby nominate Ralf Schmelter (rschmelter) to JDK Project Committer. > > Ralf is a long term member of the SAP JVM team with experience in various areas such as hotspot, garbage collection, debugging/JVMTI and many more. > > He started contributing to OpenJDK quite recently and has already piled up 13 changesets [3]. I think it's about time to make him a Committer. > > Votes are due by May 24 12:00 CET. > > Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22rschmelter%22%29%20or%20desc%28%22Contributed-by%3A%20ralf.schmelter%40sap.com%22%29%29%20and%20not%20merge%28%29&revcount=40 > From jianglizhou at google.com Fri May 10 16:32:02 2019 From: jianglizhou at google.com (Jiangli Zhou) Date: Fri, 10 May 2019 09:32:02 -0700 Subject: CFV: New JDK Committer: Ralf Schmelter In-Reply-To: References: Message-ID: Vote yes Best regards, Jiangli From: Langer, Christoph Date: Fri, May 10, 2019 at 12:52 AM To: jdk-dev Cc: Schmelter, Ralf > I hereby nominate Ralf Schmelter (rschmelter) to JDK Project Committer. > > Ralf is a long term member of the SAP JVM team with experience in various areas such as hotspot, garbage collection, debugging/JVMTI and many more. > > He started contributing to OpenJDK quite recently and has already piled up 13 changesets [3]. I think it's about time to make him a Committer. > > Votes are due by May 24 12:00 CET. > > Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22rschmelter%22%29%20or%20desc%28%22Contributed-by%3A%20ralf.schmelter%40sap.com%22%29%29%20and%20not%20merge%28%29&revcount=40 > From serguei.spitsyn at oracle.com Fri May 10 16:34:00 2019 From: serguei.spitsyn at oracle.com (serguei.spitsyn at oracle.com) Date: Fri, 10 May 2019 09:34:00 -0700 Subject: CFV: New JDK Committer: Ralf Schmelter In-Reply-To: References: Message-ID: <41ad2223-fcd1-0aec-4ee1-b9b0eb78dacc@oracle.com> Vote: yes From thomas.stuefe at gmail.com Fri May 10 19:27:00 2019 From: thomas.stuefe at gmail.com (=?UTF-8?Q?Thomas_St=C3=BCfe?=) Date: Fri, 10 May 2019 21:27:00 +0200 Subject: CFV: New JDK Committer: Ralf Schmelter In-Reply-To: <41ad2223-fcd1-0aec-4ee1-b9b0eb78dacc@oracle.com> References: <41ad2223-fcd1-0aec-4ee1-b9b0eb78dacc@oracle.com> Message-ID: Vote: yes On Fri, May 10, 2019, 6:34 PM serguei.spitsyn at oracle.com < serguei.spitsyn at oracle.com> wrote: > Vote: yes > From coleen.phillimore at oracle.com Fri May 10 20:47:27 2019 From: coleen.phillimore at oracle.com (coleen.phillimore at oracle.com) Date: Fri, 10 May 2019 16:47:27 -0400 Subject: CFV: New JDK Committer: Ralf Schmelter In-Reply-To: References: Message-ID: <78335481-7ff5-78a0-5917-d5e05ed7727f@oracle.com> Vote: yes On 5/10/19 3:51 AM, Langer, Christoph wrote: > I hereby nominate Ralf Schmelter (rschmelter) to JDK Project Committer. > > Ralf is a long term member of the SAP JVM team with experience in various areas such as hotspot, garbage collection, debugging/JVMTI and many more. > > He started contributing to OpenJDK quite recently and has already piled up 13 changesets [3]. I think it's about time to make him a Committer. > > Votes are due by May 24 12:00 CET. > > Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22rschmelter%22%29%20or%20desc%28%22Contributed-by%3A%20ralf.schmelter%40sap.com%22%29%29%20and%20not%20merge%28%29&revcount=40 > From martijnverburg at gmail.com Sat May 11 15:19:57 2019 From: martijnverburg at gmail.com (Martijn Verburg) Date: Sat, 11 May 2019 16:19:57 +0100 Subject: Announcing the Renaissance benchmark suite In-Reply-To: <8dd949e7-4f40-a7e1-efc7-eddaecf0d0fa@oracle.com> References: <1d69224f-c58f-2248-5312-95b8a9b19167@oracle.com> <1d8cfd4e-b679-cf6b-d18b-bc20123258d4@loongson.cn> <8dd949e7-4f40-a7e1-efc7-eddaecf0d0fa@oracle.com> Message-ID: Great initiative! we are adding it to the Adopt test pipelines for 8-13 - you?ll be able to track the results through our test results service in the coming weeks - trss.adoptopenjdk.net On Fri, 10 May 2019 at 12:34, Francois Farquet wrote: > Hi Jie, > > Yes, we have a Google group here : > https://groups.google.com/forum/#!forum/renaissance-dev > And a Twitter account (@RenaissanceJVM) : > https://twitter.com/renaissancejvm > > Thanks for the report about the website problems, we will fix that shortly. > > Bests, > > Francois > > Le 10.05.19 ? 11:23, Jie Fu a ?crit : > > Hi Francois, > > > > Very cool! Thanks. > > > > Is there a mailing list about Renaissance? > > > > The website could be more perfect if the following issues be fixed: > > 1) "target/scala-2.12" might be "target/renaissance-0.9.0.jar" on > > page[1] under "Building the suite". > > 2) The page link[2], which was referenced in[1] under "Contributing", > > was not found there. > > > > Best regards, > > Jie > > > > [1] > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__renaissance.dev_docs&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=A2eR84h9-mSFlGoC541LbA5ml9kGSBgXjBrlPh1tAlI&m=BmnULNn2SK9LEu1bd9fRDxZ6dJgfjEA4OtN8SjwKspI&s=2srmNs2vWiED4YXPKG4WpgSHU60NYiSBy91XRatPTzQ&e= > > [2] > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__renaissance.dev_CONTRIBUTION.md&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=A2eR84h9-mSFlGoC541LbA5ml9kGSBgXjBrlPh1tAlI&m=BmnULNn2SK9LEu1bd9fRDxZ6dJgfjEA4OtN8SjwKspI&s=p4g7Zqt4xc9mHHsTl-vVSGLBLXlIGPlBF9fjVxMHtHc&e= > > > > > > On 2019/5/9 ??4:32, Francois Farquet wrote: > >> Dear all, > >> > >> We are pleased to announce the release of the Renaissance Benchmark > >> Suite. This new suite is intended to provide workloads that are not > >> available elsewhere, and thus complement the workloads found in the > >> existing, commonly used benchmark suites for the JVM, such as DaCapo, > >> ScalaBench, and SPECjvm2008, which we gratefully acknowledge. We have > >> found a great deal of inspiration in these suites, and strive to > >> match and, where possible, exceed, the level of quality and usability > >> established by these suites. > >> > >> We aim to make the Renaissance development process as open as > >> possible, and invite the community to participate. The code is > >> open-source and the contribution mechanism is open. The suite will be > >> regularly updated through minor releases, while new benchmarks will > >> be introduced or retired in major releases. > >> > >> Version 0.9 marks the first public open-source release of the > >> Renaissance suite and is considered a major release candidate with > >> respect to the selection of workloads included in the suite. We are > >> still stabilizing the internal design until the 1.0 major release > >> which should be ready in a few weeks. In the meantime, any feedback > >> or contribution is very welcome. > >> > >> Repository : > >> > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_renaissance-2Dbenchmarks_renaissance_&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=A2eR84h9-mSFlGoC541LbA5ml9kGSBgXjBrlPh1tAlI&m=BmnULNn2SK9LEu1bd9fRDxZ6dJgfjEA4OtN8SjwKspI&s=kLdoHZOI1qQH9SbwjL52xFV4PkrkF28eWnd6kAQn12A&e= > >> Website : > >> > https://urldefense.proofpoint.com/v2/url?u=https-3A__renaissance.dev_&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=A2eR84h9-mSFlGoC541LbA5ml9kGSBgXjBrlPh1tAlI&m=BmnULNn2SK9LEu1bd9fRDxZ6dJgfjEA4OtN8SjwKspI&s=ObnqyI-MrdN6EtjHZQt8-3BTC4fIrh6m-vTVpeAljZo&e= > >> > >> Thanks, > >> > >> Francois Farquet > >> > >> > > > -- Cheers, Martijn (Sent from Gmail Mobile) From neugens.limasoftware at gmail.com Sun May 12 06:19:27 2019 From: neugens.limasoftware at gmail.com (Mario Torre) Date: Sun, 12 May 2019 08:19:27 +0200 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: Vote: Yes, Cheers, Mario On Thu 9. May 2019 at 10:08, Volker Simonis wrote: > I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. > > Matthias is a long standing member of the JVM team at SAP. He's main > areas of expertise are the build system, compilers/porting and > security updates. He's a JDK Committer who has contributed more than > 90 changes within the last two years [1]. > > Votes are due by 23 May 2019, 12:00 CET. > > Only current JDK Reviewers [2] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this > mailing list. > > For Three-Vote Consensus voting instructions, see [3]. > > Volker Simonis > > [1] > http://hg.openjdk.java.net/jdk/jdk/search/?rev=((author(%22mbaesken%22)%20and%20not%20desc(%22Contributed-by%22))%20or%20desc(%22Contributed-by%3A%20matthias.baesken%40sap.com%22))%20and%20not%20merge()&revcount=100 > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#reviewer-vote > -- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF Java Champion - Blog: http://neugens.wordpress.com - Twitter: @neugens Proud GNU Classpath developer: http://www.classpath.org/ OpenJDK: http://openjdk.java.net/projects/caciocavallo/ Please, support open standards: http://endsoftpatents.org/ From thomas.stuefe at gmail.com Mon May 13 05:10:15 2019 From: thomas.stuefe at gmail.com (=?UTF-8?Q?Thomas_St=C3=BCfe?=) Date: Mon, 13 May 2019 07:10:15 +0200 Subject: hg.openjdk.java.net/jdk not reachable Message-ID: Hi all, Since yesterday the jdk repositories seem not to be reachable. hg pull quits with 500, the web interface with some server side python error. Any ideas? Did I miss some maintenance anouncement? Thanks, Thomas From christoph.langer at sap.com Mon May 13 06:21:06 2019 From: christoph.langer at sap.com (Langer, Christoph) Date: Mon, 13 May 2019 06:21:06 +0000 Subject: hg.openjdk.java.net/jdk not reachable In-Reply-To: References: Message-ID: Hi Thomas, no idea, I can see the same... I'm copying ops, maybe they can shed some light on this or give an outlook when to expect it to be functional again. Best regards Christoph > -----Original Message----- > From: jdk-dev On Behalf Of Thomas > St?fe > Sent: Montag, 13. Mai 2019 07:10 > To: jdk-dev > Subject: hg.openjdk.java.net/jdk not reachable > > Hi all, > > Since yesterday the jdk repositories seem not to be reachable. hg pull > quits with 500, the web interface with some server side python error. > > Any ideas? Did I miss some maintenance anouncement? > > Thanks, Thomas From Alan.Bateman at oracle.com Mon May 13 06:29:16 2019 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Mon, 13 May 2019 07:29:16 +0100 Subject: hg.openjdk.java.net/jdk not reachable In-Reply-To: References: Message-ID: <53cd6a74-1a35-2a48-3f24-5a128b96086e@oracle.com> On 13/05/2019 06:10, Thomas St?fe wrote: > Hi all, > > Since yesterday the jdk repositories seem not to be reachable. hg pull > quits with 500, the web interface with some server side python error. > > Any ideas? Did I miss some maintenance anouncement? > I think this is unscheduled, seems to be in trouble since Sunday mid morning (PT). A mail was sent to ops. -Alan From francois.farquet at oracle.com Mon May 13 07:24:31 2019 From: francois.farquet at oracle.com (Francois Farquet) Date: Mon, 13 May 2019 09:24:31 +0200 Subject: Announcing the Renaissance benchmark suite In-Reply-To: References: <1d69224f-c58f-2248-5312-95b8a9b19167@oracle.com> <1d8cfd4e-b679-cf6b-d18b-bc20123258d4@loongson.cn> <8dd949e7-4f40-a7e1-efc7-eddaecf0d0fa@oracle.com> Message-ID: <2b207aae-fd2d-fc49-a63a-bbd66469bfc6@oracle.com> Thanks for doing this. Looking forward to see the first results there ! - Francois Le 11.05.19 ? 17:19, Martijn Verburg a ?crit?: > Great initiative! ?we are adding it to the Adopt test pipelines for > 8-13 - you?ll be able to track the results through our test results > service in the coming weeks ?- trss.adoptopenjdk.net > > > On Fri, 10 May 2019 at 12:34, Francois Farquet > > wrote: > > Hi Jie, > > Yes, we have a Google group here : > https://groups.google.com/forum/#!forum/renaissance-dev > > And a Twitter account (@RenaissanceJVM) : > https://twitter.com/renaissancejvm > > > Thanks for the report about the website problems, we will fix that > shortly. > > Bests, > > Francois > > Le 10.05.19 ? 11:23, Jie Fu a ?crit?: > > Hi Francois, > > > > Very cool! Thanks. > > > > Is there a mailing list about Renaissance? > > > > The website could be more perfect if the following issues be fixed: > > ?1) "target/scala-2.12" might be "target/renaissance-0.9.0.jar" on > > page[1] under "Building the suite". > > ?2) The page link[2], which was referenced in[1] under > "Contributing", > > was not found there. > > > > Best regards, > > Jie > > > > [1] > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__renaissance.dev_docs&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=A2eR84h9-mSFlGoC541LbA5ml9kGSBgXjBrlPh1tAlI&m=BmnULNn2SK9LEu1bd9fRDxZ6dJgfjEA4OtN8SjwKspI&s=2srmNs2vWiED4YXPKG4WpgSHU60NYiSBy91XRatPTzQ&e= > > [2] > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__renaissance.dev_CONTRIBUTION.md&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=A2eR84h9-mSFlGoC541LbA5ml9kGSBgXjBrlPh1tAlI&m=BmnULNn2SK9LEu1bd9fRDxZ6dJgfjEA4OtN8SjwKspI&s=p4g7Zqt4xc9mHHsTl-vVSGLBLXlIGPlBF9fjVxMHtHc&e= > > > > > > On 2019/5/9 ??4:32, Francois Farquet wrote: > >> Dear all, > >> > >> We are pleased to announce the release of the Renaissance > Benchmark > >> Suite. This new suite is intended to provide workloads that are > not > >> available elsewhere, and thus complement the workloads found in > the > >> existing, commonly used benchmark suites for the JVM, such as > DaCapo, > >> ScalaBench, and SPECjvm2008, which we gratefully acknowledge. > We have > >> found a great deal of inspiration in these suites, and strive to > >> match and, where possible, exceed, the level of quality and > usability > >> established by these suites. > >> > >> We aim to make the Renaissance development process as open as > >> possible, and invite the community to participate. The code is > >> open-source and the contribution mechanism is open. The suite > will be > >> regularly updated through minor releases, while new benchmarks > will > >> be introduced or retired in major releases. > >> > >> Version 0.9 marks the first public open-source release of the > >> Renaissance suite and is considered a major release candidate with > >> respect to the selection of workloads included in the suite. We > are > >> still stabilizing the internal design until the 1.0 major release > >> which should be ready in a few weeks. In the meantime, any > feedback > >> or contribution is very welcome. > >> > >> Repository : > >> > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_renaissance-2Dbenchmarks_renaissance_&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=A2eR84h9-mSFlGoC541LbA5ml9kGSBgXjBrlPh1tAlI&m=BmnULNn2SK9LEu1bd9fRDxZ6dJgfjEA4OtN8SjwKspI&s=kLdoHZOI1qQH9SbwjL52xFV4PkrkF28eWnd6kAQn12A&e= > >> Website : > >> > https://urldefense.proofpoint.com/v2/url?u=https-3A__renaissance.dev_&d=DwIDaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=A2eR84h9-mSFlGoC541LbA5ml9kGSBgXjBrlPh1tAlI&m=BmnULNn2SK9LEu1bd9fRDxZ6dJgfjEA4OtN8SjwKspI&s=ObnqyI-MrdN6EtjHZQt8-3BTC4fIrh6m-vTVpeAljZo&e= > >> > >> Thanks, > >> > >> Francois Farquet > >> > >> > > > > -- > Cheers, Martijn (Sent from Gmail Mobile) From Alan.Bateman at oracle.com Mon May 13 07:43:35 2019 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Mon, 13 May 2019 08:43:35 +0100 Subject: Announcing the Renaissance benchmark suite In-Reply-To: <2F21ACDC37E6D290.0D834AD5-A9BB-4012-80F0-2DF248C956F1@mail.outlook.com> References: <1d69224f-c58f-2248-5312-95b8a9b19167@oracle.com> <0c6f0406-35c7-425a-49fe-e0b4bbcd579e@oracle.com> <2F21ACDC37E6D290.0D834AD5-A9BB-4012-80F0-2DF248C956F1@mail.outlook.com> Message-ID: <3e0ae793-1d54-c8cc-cc32-f60500186607@oracle.com> On 09/05/2019 19:04, Francois Farquet wrote: > Hi Alan, > > The suite has been developed and tested under JDK8 and full support of > JDK11 is planned for the 1.0.0 release. > Regarding the latest JDK and ea versions, we?ll do our best to test it > regularly but if the Java Product Group at Oracle could regularly > check its compatibility and performance, that would be great. > From what I can tell, none of the apache-spark benchmarks will run with with any recent feature releases. They all fall over with HADOOP-14586 in code that is parsing the value of "java.version" property. The database benches seems to have issues too, seems to be code in one of Chronicle libraries trying to hack java.lang.reflect.AccessibleObject privates. Are you, or others, working with these projects to get fixes or versions that run on more recent releases, maybe as part of the effort to get it to run on JDK 11 builds? I'm only asking because most of the activity in OpenJDK is the main line, currently targeting JDK 13, and in the project repos that are developing features that will eventually go into the main line. It would be nice to be able to have the benchmark suite usable on the latest code base. It is of course useful to be able to run it on update releases too but I'm less interested in that. -Alan From thomas.stuefe at gmail.com Mon May 13 08:12:20 2019 From: thomas.stuefe at gmail.com (=?UTF-8?Q?Thomas_St=C3=BCfe?=) Date: Mon, 13 May 2019 10:12:20 +0200 Subject: hg.openjdk.java.net/jdk not reachable In-Reply-To: <53cd6a74-1a35-2a48-3f24-5a128b96086e@oracle.com> References: <53cd6a74-1a35-2a48-3f24-5a128b96086e@oracle.com> Message-ID: Thank you Alan. Lets hope it resolves quickly. On Mon, May 13, 2019 at 8:29 AM Alan Bateman wrote: > On 13/05/2019 06:10, Thomas St?fe wrote: > > Hi all, > > > > Since yesterday the jdk repositories seem not to be reachable. hg pull > > quits with 500, the web interface with some server side python error. > > > > Any ideas? Did I miss some maintenance anouncement? > > > I think this is unscheduled, seems to be in trouble since Sunday mid > morning (PT). A mail was sent to ops. > > -Alan > > From adinn at redhat.com Mon May 13 08:13:53 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 13 May 2019 09:13:53 +0100 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: <36893283-5e91-6106-99ee-2b87c0342c03@redhat.com> Vote: yes On 09/05/2019 09:07, Volker Simonis wrote: > I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. > > Matthias is a long standing member of the JVM team at SAP. He's main > areas of expertise are the build system, compilers/porting and > security updates. He's a JDK Committer who has contributed more than > 90 changes within the last two years [1]. > > Votes are due by 23 May 2019, 12:00 CET. > > Only current JDK Reviewers [2] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this > mailing list. > > For Three-Vote Consensus voting instructions, see [3]. > > Volker Simonis > > [1] http://hg.openjdk.java.net/jdk/jdk/search/?rev=((author(%22mbaesken%22)%20and%20not%20desc(%22Contributed-by%22))%20or%20desc(%22Contributed-by%3A%20matthias.baesken%40sap.com%22))%20and%20not%20merge()&revcount=100 > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#reviewer-vote > -- regards, Andrew Dinn ----------- Senior Principal Software Engineer Red Hat UK Ltd Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander From adinn at redhat.com Mon May 13 08:17:33 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 13 May 2019 09:17:33 +0100 Subject: CFV: New JDK Committer: Ralf Schmelter In-Reply-To: References: Message-ID: Vote: yes On 10/05/2019 08:51, Langer, Christoph wrote: > I hereby nominate Ralf Schmelter (rschmelter) to JDK Project Committer. > > Ralf is a long term member of the SAP JVM team with experience in various areas such as hotspot, garbage collection, debugging/JVMTI and many more. > > He started contributing to OpenJDK quite recently and has already piled up 13 changesets [3]. I think it's about time to make him a Committer. > > Votes are due by May 24 12:00 CET. > > Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22rschmelter%22%29%20or%20desc%28%22Contributed-by%3A%20ralf.schmelter%40sap.com%22%29%29%20and%20not%20merge%28%29&revcount=40 > > -- regards, Andrew Dinn ----------- Senior Principal Software Engineer Red Hat UK Ltd Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander From chris.hegarty at oracle.com Mon May 13 09:51:44 2019 From: chris.hegarty at oracle.com (Chris Hegarty) Date: Mon, 13 May 2019 10:51:44 +0100 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: <653492aa-e989-6f96-ffb2-a269977490ec@oracle.com> Vote: Yes. -Chris. From fweimer at redhat.com Mon May 13 09:54:04 2019 From: fweimer at redhat.com (Florian Weimer) Date: Mon, 13 May 2019 11:54:04 +0200 Subject: Announcing the Renaissance benchmark suite In-Reply-To: <3e0ae793-1d54-c8cc-cc32-f60500186607@oracle.com> (Alan Bateman's message of "Mon, 13 May 2019 08:43:35 +0100") References: <1d69224f-c58f-2248-5312-95b8a9b19167@oracle.com> <0c6f0406-35c7-425a-49fe-e0b4bbcd579e@oracle.com> <2F21ACDC37E6D290.0D834AD5-A9BB-4012-80F0-2DF248C956F1@mail.outlook.com> <3e0ae793-1d54-c8cc-cc32-f60500186607@oracle.com> Message-ID: <87sgtihe83.fsf@oldenburg2.str.redhat.com> * Alan Bateman: > On 09/05/2019 19:04, Francois Farquet wrote: >> Hi Alan, >> >> The suite has been developed and tested under JDK8 and full support >> of JDK11 is planned for the 1.0.0 release. >> Regarding the latest JDK and ea versions, we?ll do our best to test >> it regularly but if the Java Product Group at Oracle could regularly >> check its compatibility and performance, that would be great. >> > From what I can tell, none of the apache-spark benchmarks will run > with with any recent feature releases. They all fall over with > HADOOP-14586 in code that is parsing the value of "java.version" > property. The database benches seems to have issues too, seems to be > code in one of Chronicle libraries trying to hack > java.lang.reflect.AccessibleObject privates. Are you, or others, > working with these projects to get fixes or versions that run on more > recent releases, maybe as part of the effort to get it to run on JDK > 11 builds? This leads to the question to what extent these higher-level run-time environments are part of the benchmark. Is it expected they remain unchanged (except for such bug fixes)? Or can they be enhanced to use current and new JVM features that help with their implementation? Thanks, Florian From gromero at linux.vnet.ibm.com Mon May 13 13:25:19 2019 From: gromero at linux.vnet.ibm.com (Gustavo Romero) Date: Mon, 13 May 2019 10:25:19 -0300 Subject: CFV: New JDK Committer: Ralf Schmelter In-Reply-To: References: Message-ID: Vote: yes Best regards, Gustavo On 05/10/2019 04:51 AM, Langer, Christoph wrote: > I hereby nominate Ralf Schmelter (rschmelter) to JDK Project Committer. > > Ralf is a long term member of the SAP JVM team with experience in various areas such as hotspot, garbage collection, debugging/JVMTI and many more. > > He started contributing to OpenJDK quite recently and has already piled up 13 changesets [3]. I think it's about time to make him a Committer. > > Votes are due by May 24 12:00 CET. > > Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22rschmelter%22%29%20or%20desc%28%22Contributed-by%3A%20ralf.schmelter%40sap.com%22%29%29%20and%20not%20merge%28%29&revcount=40 From tim.bell at oracle.com Mon May 13 14:09:38 2019 From: tim.bell at oracle.com (Tim Bell) Date: Mon, 13 May 2019 07:09:38 -0700 Subject: hg.openjdk.java.net/jdk not reachable In-Reply-To: References: Message-ID: <5CD97AA2.708@oracle.com> >> Since yesterday the jdk repositories seem not to be reachable. hg pull >> quits with 500, the web interface with some server side python error. This is resolved. Please let us know on ops at openjdk.java.net if any problems continue. Tim From francois.farquet at oracle.com Mon May 13 14:10:58 2019 From: francois.farquet at oracle.com (Francois Farquet) Date: Mon, 13 May 2019 16:10:58 +0200 Subject: Announcing the Renaissance benchmark suite In-Reply-To: <87sgtihe83.fsf@oldenburg2.str.redhat.com> References: <1d69224f-c58f-2248-5312-95b8a9b19167@oracle.com> <0c6f0406-35c7-425a-49fe-e0b4bbcd579e@oracle.com> <2F21ACDC37E6D290.0D834AD5-A9BB-4012-80F0-2DF248C956F1@mail.outlook.com> <3e0ae793-1d54-c8cc-cc32-f60500186607@oracle.com> <87sgtihe83.fsf@oldenburg2.str.redhat.com> Message-ID: Le 13.05.19 ? 11:54, Florian Weimer a ?crit?: > * Alan Bateman: > >> On 09/05/2019 19:04, Francois Farquet wrote: >>> Hi Alan, >>> >>> The suite has been developed and tested under JDK8 and full support >>> of JDK11 is planned for the 1.0.0 release. >>> Regarding the latest JDK and ea versions, we?ll do our best to test >>> it regularly but if the Java Product Group at Oracle could regularly >>> check its compatibility and performance, that would be great. >>> >> From what I can tell, none of the apache-spark benchmarks will run >> with with any recent feature releases. They all fall over with >> HADOOP-14586 in code that is parsing the value of "java.version" >> property. The database benches seems to have issues too, seems to be >> code in one of Chronicle libraries trying to hack >> java.lang.reflect.AccessibleObject privates. Are you, or others, >> working with these projects to get fixes or versions that run on more >> recent releases, maybe as part of the effort to get it to run on JDK >> 11 builds? > This leads to the question to what extent these higher-level run-time > environments are part of the benchmark. Is it expected they remain > unchanged (except for such bug fixes)? Or can they be enhanced to use > current and new JVM features that help with their implementation? Each benchmark should be made as compatible as possible with all reasonable JDK versions. However, that doesn't mean there shouldn't be benchmarks that are compatible only with some late JDK version if there is a good reason for that, like the use of recent features that are representative of what a recent workload looks like. So, considering Renaissance as an evolving benchmark suite with benchmarks being added or removed from a release to another, we can imagine having some JDK version restriction per benchmark if we face that need. Regarding enhancing current benchmarks, I would advise against anything different than bug fixes. Major changes should be made as a distinct benchmark to avoid confusion. Thanks, Francois > > Thanks, > Florian From thomas.stuefe at gmail.com Mon May 13 14:31:34 2019 From: thomas.stuefe at gmail.com (=?UTF-8?Q?Thomas_St=C3=BCfe?=) Date: Mon, 13 May 2019 16:31:34 +0200 Subject: hg.openjdk.java.net/jdk not reachable In-Reply-To: <5CD97AA2.708@oracle.com> References: <5CD97AA2.708@oracle.com> Message-ID: Thank you Tim. On Mon, May 13, 2019 at 4:09 PM Tim Bell wrote: > > >> Since yesterday the jdk repositories seem not to be reachable. hg pull > >> quits with 500, the web interface with some server side python error. > > This is resolved. > > Please let us know on ops at openjdk.java.net if any problems continue. > > Tim > > > From aph at redhat.com Mon May 13 15:09:20 2019 From: aph at redhat.com (Andrew Haley) Date: Mon, 13 May 2019 16:09:20 +0100 Subject: CFV: New JDK Reviewer: Severin Gehwolf Message-ID: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> I hereby nominate Severin Gehwolf to JDK Reviewer. Severin has contributed ~60 changesets[1] to OpenJDK since 2015. Backporting work exceeds 10. This includes jdk11u and jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so far. Most contributions have been to hotspot/serviceability and build areas. Recent, yet uncommitted, work will include more container work in the JVM (cgroup v2) and a new jlink plugin. Specific changes worth mentioning: - Added Nestmates support to Zero (JEP-181)[4]. - Improved container limits dection in the JVM[5]. - Fixed a memory leak in the debugger[6]. [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() [2] https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() [3] https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 Votes are due by May 27, 2019. Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. For Lazy Consensus voting instructions, see [2]. [1] http://openjdk.java.net/census [2] http://openjdk.java.net/projects/#committer-vote -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From shade at redhat.com Mon May 13 15:11:15 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 13 May 2019 17:11:15 +0200 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: <35db41fe-f0e1-2498-fed9-4171d462af3b@redhat.com> Vote: yes On 5/13/19 5:09 PM, Andrew Haley wrote: > I hereby nominate Severin Gehwolf to JDK Reviewer. -Aleksey From goetz.lindenmaier at sap.com Mon May 13 15:12:54 2019 From: goetz.lindenmaier at sap.com (Lindenmaier, Goetz) Date: Mon, 13 May 2019 15:12:54 +0000 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: vote: yes Best, Goetz > -----Original Message----- > From: jdk-dev On Behalf Of Andrew > Haley > Sent: Montag, 13. Mai 2019 17:09 > To: jdk-dev at openjdk.java.net > Subject: CFV: New JDK Reviewer: Severin Gehwolf > > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] > https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf) > +or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] > https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgeh > wolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(s > gehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=- > 2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%2 > 0ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > > -- > Andrew Haley > Java Platform Lead Engineer > Red Hat UK Ltd. > EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From thomas.stuefe at gmail.com Mon May 13 15:14:06 2019 From: thomas.stuefe at gmail.com (=?UTF-8?Q?Thomas_St=C3=BCfe?=) Date: Mon, 13 May 2019 17:14:06 +0200 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: Vote: yes On Mon, May 13, 2019 at 5:09 PM Andrew Haley wrote: > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] > https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] > https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] > https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > > -- > Andrew Haley > Java Platform Lead Engineer > Red Hat UK Ltd. > EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 > From zgu at redhat.com Mon May 13 15:18:00 2019 From: zgu at redhat.com (Zhengyu Gu) Date: Mon, 13 May 2019 11:18:00 -0400 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: Vote: yes. -Zhengyu On 5/13/19 11:09 AM, Andrew Haley wrote: > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > From jianglizhou at google.com Mon May 13 15:28:56 2019 From: jianglizhou at google.com (Jiangli Zhou) Date: Mon, 13 May 2019 08:28:56 -0700 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: Vote: yes Best Regards, Jiangli From: Andrew Haley Date: Mon, May 13, 2019 at 8:09 AM To: jdk-dev at openjdk.java.net > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > > -- > Andrew Haley > Java Platform Lead Engineer > Red Hat UK Ltd. > EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From lois.foltan at oracle.com Mon May 13 15:33:01 2019 From: lois.foltan at oracle.com (Lois Foltan) Date: Mon, 13 May 2019 11:33:01 -0400 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: Vote: yes On 5/13/2019 11:09 AM, Andrew Haley wrote: > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > From lois.foltan at oracle.com Mon May 13 15:34:02 2019 From: lois.foltan at oracle.com (Lois Foltan) Date: Mon, 13 May 2019 11:34:02 -0400 Subject: CFV: New JDK Committer: Ralf Schmelter In-Reply-To: References: Message-ID: <142bee0a-656a-b8a0-9061-1ae60b30cec8@oracle.com> Vote: yes On 5/10/2019 3:51 AM, Langer, Christoph wrote: > I hereby nominate Ralf Schmelter (rschmelter) to JDK Project Committer. > > Ralf is a long term member of the SAP JVM team with experience in various areas such as hotspot, garbage collection, debugging/JVMTI and many more. > > He started contributing to OpenJDK quite recently and has already piled up 13 changesets [3]. I think it's about time to make him a Committer. > > Votes are due by May 24 12:00 CET. > > Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22rschmelter%22%29%20or%20desc%28%22Contributed-by%3A%20ralf.schmelter%40sap.com%22%29%29%20and%20not%20merge%28%29&revcount=40 > From adinn at redhat.com Mon May 13 15:35:09 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 13 May 2019 16:35:09 +0100 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: Vote: yes On 13/05/2019 16:09, Andrew Haley wrote: > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > -- regards, Andrew Dinn ----------- Senior Principal Software Engineer Red Hat UK Ltd Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander From martin.doerr at sap.com Mon May 13 15:36:46 2019 From: martin.doerr at sap.com (Doerr, Martin) Date: Mon, 13 May 2019 15:36:46 +0000 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <35db41fe-f0e1-2498-fed9-4171d462af3b@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> <35db41fe-f0e1-2498-fed9-4171d462af3b@redhat.com> Message-ID: Vote: yes Best regards, Martin From volker.simonis at gmail.com Mon May 13 15:40:17 2019 From: volker.simonis at gmail.com (Volker Simonis) Date: Mon, 13 May 2019 17:40:17 +0200 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: Vote: yes On Mon, May 13, 2019 at 5:09 PM Andrew Haley wrote: > > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > > -- > Andrew Haley > Java Platform Lead Engineer > Red Hat UK Ltd. > EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From andy.herrick at oracle.com Mon May 13 15:46:46 2019 From: andy.herrick at oracle.com (Andy Herrick) Date: Mon, 13 May 2019 11:46:46 -0400 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: <76eba2ea-14a1-b06d-4f10-947ff2e67d1d@oracle.com> Vote:? yes /Andy On 5/13/2019 11:09 AM, Andrew Haley wrote: > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > From rwestrel at redhat.com Mon May 13 15:52:43 2019 From: rwestrel at redhat.com (Roland Westrelin) Date: Mon, 13 May 2019 17:52:43 +0200 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: <874l5ymjw4.fsf@redhat.com> Vote: yes Roland. From vladimir.kozlov at oracle.com Mon May 13 16:13:19 2019 From: vladimir.kozlov at oracle.com (Vladimir Kozlov) Date: Mon, 13 May 2019 09:13:19 -0700 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: <74A6AFB2-1E1E-4E9F-AD52-E0438197C2C7@oracle.com> Vote yes Thanks Vladimir > On May 13, 2019, at 8:09 AM, Andrew Haley wrote: > > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > > -- > Andrew Haley > Java Platform Lead Engineer > Red Hat UK Ltd. > EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From Alan.Bateman at oracle.com Mon May 13 17:22:37 2019 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Mon, 13 May 2019 18:22:37 +0100 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: <7bc36298-1d1c-7a7d-0c16-34ead2eba09c@oracle.com> Vote: yes From serguei.spitsyn at oracle.com Mon May 13 20:04:24 2019 From: serguei.spitsyn at oracle.com (serguei.spitsyn at oracle.com) Date: Mon, 13 May 2019 13:04:24 -0700 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: <3e4c53a1-b35e-b5af-1d75-81cc239a7b1f@oracle.com> Vote: yes From david.holmes at oracle.com Tue May 14 06:06:29 2019 From: david.holmes at oracle.com (David Holmes) Date: Tue, 14 May 2019 16:06:29 +1000 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: <6f95c6bf-3d76-a1ef-23ba-97f5664c211a@oracle.com> Vote: yes David On 14/05/2019 1:09 am, Andrew Haley wrote: > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > From christoph.langer at sap.com Tue May 14 07:00:10 2019 From: christoph.langer at sap.com (Langer, Christoph) Date: Tue, 14 May 2019 07:00:10 +0000 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: Vote: yes /Christoph > -----Original Message----- > From: jdk-dev On Behalf Of Andrew > Haley > Sent: Montag, 13. Mai 2019 17:09 > To: jdk-dev at openjdk.java.net > Subject: CFV: New JDK Reviewer: Severin Gehwolf > > I hereby nominate Severin Gehwolf to JDK > Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] > https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehw > olf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] > https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sg > ehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(auth > or(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=- > 2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf% > 20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > > -- > Andrew Haley > Java Platform Lead Engineer > Red Hat UK Ltd. > EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From daniel.fuchs at oracle.com Tue May 14 10:28:48 2019 From: daniel.fuchs at oracle.com (Daniel Fuchs) Date: Tue, 14 May 2019 11:28:48 +0100 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: Vote: yes best regards, -- daniel On 13/05/2019 16:09, Andrew Haley wrote: > I hereby nominate Severin Gehwolf to JDK Reviewer. From sean.coffey at oracle.com Tue May 14 10:59:58 2019 From: sean.coffey at oracle.com (=?UTF-8?Q?Se=c3=a1n_Coffey?=) Date: Tue, 14 May 2019 11:59:58 +0100 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: <1f11605d-82ed-7971-36f3-96062dcda2c5@oracle.com> Vote: yes regards, Sean. On 13/05/2019 16:09, Andrew Haley wrote: > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > From gnu.andrew at redhat.com Tue May 14 14:37:39 2019 From: gnu.andrew at redhat.com (Andrew John Hughes) Date: Tue, 14 May 2019 15:37:39 +0100 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: <8e4bfb30-46a1-8424-b9ee-117ffef0d0f8@redhat.com> On 13/05/2019 16:09, Andrew Haley wrote: > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > Vote: Yes. -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 https://keybase.io/gnu_andrew From kim.barrett at oracle.com Tue May 14 19:23:19 2019 From: kim.barrett at oracle.com (Kim Barrett) Date: Tue, 14 May 2019 15:23:19 -0400 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: <8C63D049-055E-4271-8C96-EFF117937288@oracle.com> vote: yes > On May 13, 2019, at 11:09 AM, Andrew Haley wrote: > > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > > -- > Andrew Haley > Java Platform Lead Engineer > Red Hat UK Ltd. > EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From peter.levart at gmail.com Tue May 14 20:23:11 2019 From: peter.levart at gmail.com (Peter Levart) Date: Tue, 14 May 2019 22:23:11 +0200 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: Vote: yes Regards, Peter On 5/13/19 5:09 PM, Andrew Haley wrote: > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > From chenshanyao at huawei.com Wed May 15 03:11:44 2019 From: chenshanyao at huawei.com (Chenshanyao) Date: Wed, 15 May 2019 03:11:44 +0000 Subject: About JCK access request Message-ID: Hi, guys I'm from Huawei Technologie co., Ltd. Huawei is a member of Linaro, we're doing a distribution based on OpenJDK. The builds would be targeted on Huawei's server, including aarch64 and x86_64. Huawei has signed OCA and OCTLA V2.0 in 2016, and have got access to the JCK8 (https://openjdk.java.net/groups/conformance/JckAccess/jck-access.html). About half year ago, we sent several emails to oracle-ca_us at oracle.com to get access to the jck for java 9 or later, no reply has been received. It's blocking our progress on jdk11 compatibility test. We have no idea how long will it take, is there anything we can do but wait? Best Regards! Chen Shanyao From aoqi at loongson.cn Wed May 15 03:55:23 2019 From: aoqi at loongson.cn (Ao Qi) Date: Wed, 15 May 2019 11:55:23 +0800 Subject: About JCK access request In-Reply-To: References: Message-ID: Hi Chen Shanyao, 1. Huawei (and Linaro) is not on "Signatories for Java SE 9, or later" list [1] at present. I think you should sign OCTLA v3.0 for JCK 9 and later. 2. There is a private list conformance-octla-private at openjdk.java.net for JCK issues. Cheers, Ao Qi [1] http://openjdk.java.net/groups/conformance/JckAccess/jck-access.html On Wed, May 15, 2019 at 11:11 AM Chenshanyao wrote: > > Hi, guys > > I'm from Huawei Technologie co., Ltd. Huawei is a member of Linaro, we're doing a distribution based on OpenJDK. The builds would be targeted on Huawei's server, including aarch64 and x86_64. > > Huawei has signed OCA and OCTLA V2.0 in 2016, and have got access to the JCK8 (https://openjdk.java.net/groups/conformance/JckAccess/jck-access.html). About half year ago, we sent several emails to oracle-ca_us at oracle.com to get access to the jck for java 9 or later, no reply has been received. > > It's blocking our progress on jdk11 compatibility test. We have no idea how long will it take, is there anything we can do but wait? > > Best Regards! > Chen Shanyao From chenshanyao at huawei.com Wed May 15 06:52:12 2019 From: chenshanyao at huawei.com (Chenshanyao) Date: Wed, 15 May 2019 06:52:12 +0000 Subject: About JCK access request Message-ID: Hi Ao Qi, Thanks for your reply. A signed copy of the OCTLA License V3.0 has been ready, we can send it to Oracle any time as long as we received their reply. I will send an email to the private list you provided for help. Best Regards Chen Shanyao -----????----- ???: Ao Qi [mailto:aoqi at loongson.cn] ????: 2019?5?15? 11:55 ???: Chenshanyao ??: jdk-dev at openjdk.java.net ??: Re: About JCK access request Hi Chen Shanyao, 1. Huawei (and Linaro) is not on "Signatories for Java SE 9, or later" list [1] at present. I think you should sign OCTLA v3.0 for JCK 9 and later. 2. There is a private list conformance-octla-private at openjdk.java.net for JCK issues. Cheers, Ao Qi [1] http://openjdk.java.net/groups/conformance/JckAccess/jck-access.html On Wed, May 15, 2019 at 11:11 AM Chenshanyao wrote: > > Hi, guys > > I'm from Huawei Technologie co., Ltd. Huawei is a member of Linaro, we're doing a distribution based on OpenJDK. The builds would be targeted on Huawei's server, including aarch64 and x86_64. > > Huawei has signed OCA and OCTLA V2.0 in 2016, and have got access to the JCK8 (https://openjdk.java.net/groups/conformance/JckAccess/jck-access.html). About half year ago, we sent several emails to oracle-ca_us at oracle.com to get access to the jck for java 9 or later, no reply has been received. > > It's blocking our progress on jdk11 compatibility test. We have no idea how long will it take, is there anything we can do but wait? > > Best Regards! > Chen Shanyao From christoph.langer at sap.com Thu May 16 09:22:38 2019 From: christoph.langer at sap.com (Langer, Christoph) Date: Thu, 16 May 2019 09:22:38 +0000 Subject: CFV: New JDK Committer: Ichiroh Takiguchi Message-ID: I hereby nominate Ichiroh Takiguchi (itakiguchi) to JDK Committer. Ichiroh is a member of the IBM JDK team and has contributed several changes in the area of AWT/X11 and code page support. You can view his track record in the jdk repo at [3]. Votes are due by May, 30th, 2019 12:00 CET. Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. For Lazy Consensus voting instructions, see [2]. Christoph Langer [1] http://openjdk.java.net/census [2] http://openjdk.java.net/projects/#committer-vote [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22itakiguchi%22%29%20or%20desc%28%22Contributed-by%3A%20takiguc%40linux.vnet.ibm.com%22%29%29%20and%20not%20merge%28%29&revcount=80 From martin.doerr at sap.com Thu May 16 09:56:14 2019 From: martin.doerr at sap.com (Doerr, Martin) Date: Thu, 16 May 2019 09:56:14 +0000 Subject: CFV: New JDK Committer: Ichiroh Takiguchi In-Reply-To: References: Message-ID: Vote: yes Best regards, Martin From thomas.stuefe at gmail.com Thu May 16 10:12:20 2019 From: thomas.stuefe at gmail.com (=?UTF-8?Q?Thomas_St=C3=BCfe?=) Date: Thu, 16 May 2019 12:12:20 +0200 Subject: CFV: New JDK Committer: Ichiroh Takiguchi In-Reply-To: References: Message-ID: Vote: yes On Thu, May 16, 2019, 11:23 Langer, Christoph wrote: > I hereby nominate Ichiroh Takiguchi (itakiguchi) to JDK Committer. > > Ichiroh is a member of the IBM JDK team and has contributed several > changes in the area of AWT/X11 and code page support. You can view his > track record in the jdk repo at [3]. > > Votes are due by May, 30th, 2019 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] > http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22itakiguchi%22%29%20or%20desc%28%22Contributed-by%3A%20takiguc%40linux.vnet.ibm.com%22%29%29%20and%20not%20merge%28%29&revcount=80 > > From volker.simonis at gmail.com Thu May 16 10:15:19 2019 From: volker.simonis at gmail.com (Volker Simonis) Date: Thu, 16 May 2019 12:15:19 +0200 Subject: CFV: New JDK Committer: Ichiroh Takiguchi In-Reply-To: References: Message-ID: Vote: yes On Thu, May 16, 2019 at 11:23 AM Langer, Christoph wrote: > > I hereby nominate Ichiroh Takiguchi (itakiguchi) to JDK Committer. > > Ichiroh is a member of the IBM JDK team and has contributed several changes in the area of AWT/X11 and code page support. You can view his track record in the jdk repo at [3]. > > Votes are due by May, 30th, 2019 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22itakiguchi%22%29%20or%20desc%28%22Contributed-by%3A%20takiguc%40linux.vnet.ibm.com%22%29%29%20and%20not%20merge%28%29&revcount=80 > From jayathirth.d.v at oracle.com Thu May 16 10:16:45 2019 From: jayathirth.d.v at oracle.com (Jayathirth Rao) Date: Thu, 16 May 2019 15:46:45 +0530 Subject: CFV: New JDK Committer: Ichiroh Takiguchi In-Reply-To: References: Message-ID: <511F7135-AC9F-48A6-9E70-92B9166FA436@oracle.com> Vote : Yes Thanks, Jay > On 16-May-2019, at 2:52 PM, Langer, Christoph wrote: > > I hereby nominate Ichiroh Takiguchi (itakiguchi) to JDK Committer. > > Ichiroh is a member of the IBM JDK team and has contributed several changes in the area of AWT/X11 and code page support. You can view his track record in the jdk repo at [3]. > > Votes are due by May, 30th, 2019 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22itakiguchi%22%29%20or%20desc%28%22Contributed-by%3A%20takiguc%40linux.vnet.ibm.com%22%29%29%20and%20not%20merge%28%29&revcount=80 > From dmitry.markov at oracle.com Thu May 16 11:09:57 2019 From: dmitry.markov at oracle.com (Dmitry Markov) Date: Thu, 16 May 2019 12:09:57 +0100 Subject: CFV: New JDK Committer: Ichiroh Takiguchi In-Reply-To: References: Message-ID: <31FFB597-1147-4C35-9B09-9E30CAACF0B8@oracle.com> Vote: yes Thanks, Dmitry > On 16 May 2019, at 10:22, Langer, Christoph wrote: > > I hereby nominate Ichiroh Takiguchi (itakiguchi) to JDK Committer. > > Ichiroh is a member of the IBM JDK team and has contributed several changes in the area of AWT/X11 and code page support. You can view his track record in the jdk repo at [3]. > > Votes are due by May, 30th, 2019 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22itakiguchi%22%29%20or%20desc%28%22Contributed-by%3A%20takiguc%40linux.vnet.ibm.com%22%29%29%20and%20not%20merge%28%29&revcount=80 > From gromero at linux.vnet.ibm.com Thu May 16 12:39:44 2019 From: gromero at linux.vnet.ibm.com (Gustavo Romero) Date: Thu, 16 May 2019 09:39:44 -0300 Subject: CFV: New JDK Committer: Ichiroh Takiguchi In-Reply-To: References: Message-ID: Vote: yes Best regards, Gustavo On 05/16/2019 06:22 AM, Langer, Christoph wrote: > I hereby nominate Ichiroh Takiguchi (itakiguchi) to JDK Committer. > > Ichiroh is a member of the IBM JDK team and has contributed several changes in the area of AWT/X11 and code page support. You can view his track record in the jdk repo at [3]. > > Votes are due by May, 30th, 2019 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22itakiguchi%22%29%20or%20desc%28%22Contributed-by%3A%20takiguc%40linux.vnet.ibm.com%22%29%29%20and%20not%20merge%28%29&revcount=80 > From goetz.lindenmaier at sap.com Thu May 16 12:47:03 2019 From: goetz.lindenmaier at sap.com (Lindenmaier, Goetz) Date: Thu, 16 May 2019 12:47:03 +0000 Subject: CFV: New JDK Committer: Ichiroh Takiguchi In-Reply-To: References: , Message-ID: <0A629DD2-5F74-4CFC-B933-3D807F8E02E4@sap.com> Vote: yes Best, Goetz > Am 16.05.2019 um 14:41 schrieb Gustavo Romero : > > Vote: yes > > Best regards, > Gustavo > >> On 05/16/2019 06:22 AM, Langer, Christoph wrote: >> I hereby nominate Ichiroh Takiguchi (itakiguchi) to JDK Committer. >> Ichiroh is a member of the IBM JDK team and has contributed several changes in the area of AWT/X11 and code page support. You can view his track record in the jdk repo at [3]. >> Votes are due by May, 30th, 2019 12:00 CET. >> Only current JDK Committers [1] are eligible to vote >> on this nomination. Votes must be cast in the open by replying >> to this mailing list. >> For Lazy Consensus voting instructions, see [2]. >> Christoph Langer >> [1] http://openjdk.java.net/census >> [2] http://openjdk.java.net/projects/#committer-vote >> [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22itakiguchi%22%29%20or%20desc%28%22Contributed-by%3A%20takiguc%40linux.vnet.ibm.com%22%29%29%20and%20not%20merge%28%29&revcount=80 > From sgehwolf at redhat.com Thu May 16 14:04:09 2019 From: sgehwolf at redhat.com (Severin Gehwolf) Date: Thu, 16 May 2019 16:04:09 +0200 Subject: CFV: New JDK Committer: Ichiroh Takiguchi In-Reply-To: References: Message-ID: <7b1c0ced83e6d407382a2df8d298e59b348ad9f0.camel@redhat.com> Vote: yes On Thu, 2019-05-16 at 09:22 +0000, Langer, Christoph wrote: > I hereby nominate Ichiroh Takiguchi (itakiguchi) to JDK Committer. From naoto.sato at oracle.com Thu May 16 15:45:19 2019 From: naoto.sato at oracle.com (naoto.sato at oracle.com) Date: Thu, 16 May 2019 08:45:19 -0700 Subject: CFV: New JDK Committer: Ichiroh Takiguchi In-Reply-To: References: Message-ID: <7b5ccd75-7c7f-7b1e-b284-1e3a2055a37b@oracle.com> Vote: yes Naoto On 5/16/19 2:22 AM, Langer, Christoph wrote: > I hereby nominate Ichiroh Takiguchi (itakiguchi) to JDK Committer. > > Ichiroh is a member of the IBM JDK team and has contributed several changes in the area of AWT/X11 and code page support. You can view his track record in the jdk repo at [3]. > > Votes are due by May, 30th, 2019 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22itakiguchi%22%29%20or%20desc%28%22Contributed-by%3A%20takiguc%40linux.vnet.ibm.com%22%29%29%20and%20not%20merge%28%29&revcount=80 > From mark.reinhold at oracle.com Thu May 16 19:56:14 2019 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Thu, 16 May 2019 12:56:14 -0700 (PDT) Subject: JEP proposed to target JDK 13: 353: Reimplement the Legacy Socket API Message-ID: <20190516195614.B341C2AF56C@eggemoggin.niobe.net> The following JEP is proposed to target JDK 13: 353: Reimplement the Legacy Socket API https://openjdk.java.net/jeps/353 Feedback on this proposal from JDK Project Committers and Reviewers [1] is more than welcome, as are reasoned objections. If no such objections are raised by 23:00 UTC on Thursday, 23 May, or if they?re raised and then satisfactorily answered, then per the JEP 2.0 process proposal [2] I?ll target this JEP to JDK 13. - Mark [1] https://openjdk.java.net/census#jdk [2] https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html From martin.doerr at sap.com Fri May 17 08:09:36 2019 From: martin.doerr at sap.com (Doerr, Martin) Date: Fri, 17 May 2019 08:09:36 +0000 Subject: CFV: New JDK Committer: Richard Reingruber Message-ID: I hereby nominate Richard Reingruber (rrich) to JDK Committer. Richard is a long term member of the SAP JVM team with experience in various areas of hotspot like runtime, C1 and C2 compilers, garbage collection, debugging/JVMTI, s390 platform code. He already contributed 9 changes to OpenJDK [3] and he's working on further contributions. I think it's time to make him a Committer. Votes are due by May 31 12:00 CET. Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. For Lazy Consensus voting instructions, see [2]. Martin Doerr [1] http://openjdk.java.net/census [2] http://openjdk.java.net/projects/#committer-vote [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=(author(%22rrich%22)%20or%20desc(%22Contributed-by%3A%20richard.reingruber%40sap.com%22))%20and%20not%20merge()&revcount=40 From volker.simonis at gmail.com Fri May 17 08:19:44 2019 From: volker.simonis at gmail.com (Volker Simonis) Date: Fri, 17 May 2019 10:19:44 +0200 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: Vote: yes On Fri, May 17, 2019 at 10:10 AM Doerr, Martin wrote: > > I hereby nominate Richard Reingruber (rrich) to JDK Committer. > > Richard is a long term member of the SAP JVM team with experience in various areas of hotspot like runtime, C1 and C2 compilers, garbage collection, debugging/JVMTI, s390 platform code. > > He already contributed 9 changes to OpenJDK [3] and he's working on further contributions. I think it's time to make him a Committer. > > Votes are due by May 31 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Martin Doerr > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=(author(%22rrich%22)%20or%20desc(%22Contributed-by%3A%20richard.reingruber%40sap.com%22))%20and%20not%20merge()&revcount=40 > From goetz.lindenmaier at sap.com Fri May 17 08:29:35 2019 From: goetz.lindenmaier at sap.com (Lindenmaier, Goetz) Date: Fri, 17 May 2019 08:29:35 +0000 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: vote: yes Best regards, Goetz. > -----Original Message----- > From: jdk-dev On Behalf Of Doerr, > Martin > Sent: Freitag, 17. Mai 2019 10:10 > To: jdk-dev at openjdk.java.net > Subject: [CAUTION] CFV: New JDK Committer: Richard Reingruber > > I hereby nominate Richard Reingruber (rrich) to JDK Committer. > > Richard is a long term member of the SAP JVM team with experience in various > areas of hotspot like runtime, C1 and C2 compilers, garbage collection, > debugging/JVMTI, s390 platform code. > > He already contributed 9 changes to OpenJDK [3] and he's working on further > contributions. I think it's time to make him a Committer. > > Votes are due by May 31 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Martin Doerr > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] > http://hg.openjdk.java.net/jdk/jdk/search/?rev=(author(%22rrich%22)%20or% > 20desc(%22Contributed- > by%3A%20richard.reingruber%40sap.com%22))%20and%20not%20merge()&r > evcount=40 From adinn at redhat.com Fri May 17 09:25:11 2019 From: adinn at redhat.com (Andrew Dinn) Date: Fri, 17 May 2019 10:25:11 +0100 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: <6dc51a72-8707-3239-7387-a1b2511a6f76@redhat.com> Vote: yes On 17/05/2019 09:09, Doerr, Martin wrote: > I hereby nominate Richard Reingruber (rrich) to JDK Committer. > > Richard is a long term member of the SAP JVM team with experience in various areas of hotspot like runtime, C1 and C2 compilers, garbage collection, debugging/JVMTI, s390 platform code. > > He already contributed 9 changes to OpenJDK [3] and he's working on further contributions. I think it's time to make him a Committer. > > Votes are due by May 31 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Martin Doerr > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=(author(%22rrich%22)%20or%20desc(%22Contributed-by%3A%20richard.reingruber%40sap.com%22))%20and%20not%20merge()&revcount=40 > > -- regards, Andrew Dinn ----------- Senior Principal Software Engineer Red Hat UK Ltd Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander From shade at redhat.com Fri May 17 10:08:59 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Fri, 17 May 2019 12:08:59 +0200 Subject: New JDK Committer: Boris Ulasevich Message-ID: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be able to push the fixes without involving sponsors. Votes are due by June 1 12:00 CET. Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. For Lazy Consensus voting instructions, see [2]. -Aleksey Shipilev [1] http://openjdk.java.net/census [2] http://openjdk.java.net/projects/#committer-vote [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 From shade at redhat.com Fri May 17 10:09:45 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Fri, 17 May 2019 12:09:45 +0200 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> Message-ID: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Dang, missed "CFV: " from the subject, corrected. Please reply to this one. -Aleksey On 5/17/19 12:08 PM, Aleksey Shipilev wrote: > I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. > > Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed > 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be > able to push the fixes without involving sponsors. > > Votes are due by June 1 12:00 CET. > > Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the > open by replying to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > -Aleksey Shipilev > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] > http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 From roman at kennke.org Fri May 17 10:24:20 2019 From: roman at kennke.org (Roman Kennke) Date: Fri, 17 May 2019 12:24:20 +0200 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: <2586c7e5-f837-6b1b-8d3e-1078424911f5@kennke.org> Vote: yes > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > -Aleksey > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: >> I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. >> >> Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed >> 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be >> able to push the fixes without involving sponsors. >> >> Votes are due by June 1 12:00 CET. >> >> Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the >> open by replying to this mailing list. >> >> For Lazy Consensus voting instructions, see [2]. >> >> -Aleksey Shipilev >> >> [1] http://openjdk.java.net/census >> [2] http://openjdk.java.net/projects/#committer-vote >> [3] >> http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 > > From volker.simonis at gmail.com Fri May 17 10:36:01 2019 From: volker.simonis at gmail.com (Volker Simonis) Date: Fri, 17 May 2019 12:36:01 +0200 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: Vote: yes On Fri, May 17, 2019 at 12:10 PM Aleksey Shipilev wrote: > > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > -Aleksey > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: > > I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. > > > > Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed > > 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be > > able to push the fixes without involving sponsors. > > > > Votes are due by June 1 12:00 CET. > > > > Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the > > open by replying to this mailing list. > > > > For Lazy Consensus voting instructions, see [2]. > > > > -Aleksey Shipilev > > > > [1] http://openjdk.java.net/census > > [2] http://openjdk.java.net/projects/#committer-vote > > [3] > > http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 > From thomas.stuefe at gmail.com Fri May 17 10:49:04 2019 From: thomas.stuefe at gmail.com (=?UTF-8?Q?Thomas_St=C3=BCfe?=) Date: Fri, 17 May 2019 12:49:04 +0200 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: Vote: yes On Fri, May 17, 2019, 12:10 Aleksey Shipilev wrote: > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > -Aleksey > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: > > I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. > > > > Boris is the member of BellSoft JVM team with experience in x86_32 and > ARM32. He already contributed > > 32 changes to OpenJDK [3] that improved the OpenJDK support on those > platforms, and he should be > > able to push the fixes without involving sponsors. > > > > Votes are due by June 1 12:00 CET. > > > > Only current JDK Committers [1] are eligible to vote on this > nomination. Votes must be cast in the > > open by replying to this mailing list. > > > > For Lazy Consensus voting instructions, see [2]. > > > > -Aleksey Shipilev > > > > [1] http://openjdk.java.net/census > > [2] http://openjdk.java.net/projects/#committer-vote > > [3] > > > http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 > > From thomas.stuefe at gmail.com Fri May 17 10:49:29 2019 From: thomas.stuefe at gmail.com (=?UTF-8?Q?Thomas_St=C3=BCfe?=) Date: Fri, 17 May 2019 12:49:29 +0200 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: Vote: yes On Fri, May 17, 2019, 10:10 Doerr, Martin wrote: > I hereby nominate Richard Reingruber (rrich) to JDK Committer. > > Richard is a long term member of the SAP JVM team with experience in > various areas of hotspot like runtime, C1 and C2 compilers, garbage > collection, debugging/JVMTI, s390 platform code. > > He already contributed 9 changes to OpenJDK [3] and he's working on > further contributions. I think it's time to make him a Committer. > > Votes are due by May 31 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Martin Doerr > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] > http://hg.openjdk.java.net/jdk/jdk/search/?rev=(author(%22rrich%22)%20or%20desc(%22Contributed-by%3A%20richard.reingruber%40sap.com%22))%20and%20not%20merge()&revcount=40 > > From david.holmes at oracle.com Fri May 17 10:52:02 2019 From: david.holmes at oracle.com (David Holmes) Date: Fri, 17 May 2019 20:52:02 +1000 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: <05eac729-e744-21fc-8f42-de4ea3e133e2@oracle.com> Vote: yes! David On 17/05/2019 8:09 pm, Aleksey Shipilev wrote: > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > -Aleksey > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: >> I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. >> >> Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed >> 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be >> able to push the fixes without involving sponsors. >> >> Votes are due by June 1 12:00 CET. >> >> Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the >> open by replying to this mailing list. >> >> For Lazy Consensus voting instructions, see [2]. >> >> -Aleksey Shipilev >> >> [1] http://openjdk.java.net/census >> [2] http://openjdk.java.net/projects/#committer-vote >> [3] >> http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 > From david.holmes at oracle.com Fri May 17 10:52:28 2019 From: david.holmes at oracle.com (David Holmes) Date: Fri, 17 May 2019 20:52:28 +1000 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: Vote: yes David On 17/05/2019 6:09 pm, Doerr, Martin wrote: > I hereby nominate Richard Reingruber (rrich) to JDK Committer. > > Richard is a long term member of the SAP JVM team with experience in various areas of hotspot like runtime, C1 and C2 compilers, garbage collection, debugging/JVMTI, s390 platform code. > > He already contributed 9 changes to OpenJDK [3] and he's working on further contributions. I think it's time to make him a Committer. > > Votes are due by May 31 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Martin Doerr > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=(author(%22rrich%22)%20or%20desc(%22Contributed-by%3A%20richard.reingruber%40sap.com%22))%20and%20not%20merge()&revcount=40 > From matthias.baesken at sap.com Fri May 17 10:55:34 2019 From: matthias.baesken at sap.com (Baesken, Matthias) Date: Fri, 17 May 2019 10:55:34 +0000 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: Vote : yes Matthias > > > I hereby nominate Richard Reingruber (rrich) to JDK Committer. > > > > Richard is a long term member of the SAP JVM team with experience in > > various areas of hotspot like runtime, C1 and C2 compilers, garbage > > collection, debugging/JVMTI, s390 platform code. > > > > He already contributed 9 changes to OpenJDK [3] and he's working on > > further contributions. I think it's time to make him a Committer. > > > > Votes are due by May 31 12:00 CET. > > > > Only current JDK Committers [1] are eligible to vote > > on this nomination. Votes must be cast in the open by replying > > to this mailing list. > > > > For Lazy Consensus voting instructions, see [2]. > > > > Martin Doerr > > > > [1] http://openjdk.java.net/census > > [2] http://openjdk.java.net/projects/#committer-vote > > [3] > > > http://hg.openjdk.java.net/jdk/jdk/search/?rev=(author(%22rrich%22)%20o > r%20desc(%22Contributed- > by%3A%20richard.reingruber%40sap.com%22))%20and%20not%20merge()& > revcount=40 > > > > From sgehwolf at redhat.com Fri May 17 11:01:02 2019 From: sgehwolf at redhat.com (Severin Gehwolf) Date: Fri, 17 May 2019 13:01:02 +0200 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: Vote: yes From sgehwolf at redhat.com Fri May 17 11:02:14 2019 From: sgehwolf at redhat.com (Severin Gehwolf) Date: Fri, 17 May 2019 13:02:14 +0200 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: <3ca1ff39c0349623453690b14cb166365486cc11.camel@redhat.com> Vote: yes On Fri, 2019-05-17 at 12:09 +0200, Aleksey Shipilev wrote: > > I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. From dmitrij.pochepko at bell-sw.com Fri May 17 11:20:51 2019 From: dmitrij.pochepko at bell-sw.com (Dmitrij Pochepko) Date: Fri, 17 May 2019 14:20:51 +0300 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: <297fc098-7d67-c0f3-913b-f67356280203@bell-sw.com> Vote: yes On 17/05/2019 1:09 PM, Aleksey Shipilev wrote: > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > -Aleksey > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: >> I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. >> >> Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed >> 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be >> able to push the fixes without involving sponsors. >> >> Votes are due by June 1 12:00 CET. >> >> Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the >> open by replying to this mailing list. >> >> For Lazy Consensus voting instructions, see [2]. >> >> -Aleksey Shipilev >> >> [1] http://openjdk.java.net/census >> [2] http://openjdk.java.net/projects/#committer-vote >> [3] >> http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 From adinn at redhat.com Fri May 17 12:03:49 2019 From: adinn at redhat.com (Andrew Dinn) Date: Fri, 17 May 2019 13:03:49 +0100 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: Vote: yes On 17/05/2019 11:09, Aleksey Shipilev wrote: > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > -Aleksey > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: >> I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. >> >> Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed >> 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be >> able to push the fixes without involving sponsors. >> >> Votes are due by June 1 12:00 CET. >> >> Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the >> open by replying to this mailing list. >> >> For Lazy Consensus voting instructions, see [2]. >> >> -Aleksey Shipilev >> >> [1] http://openjdk.java.net/census >> [2] http://openjdk.java.net/projects/#committer-vote >> [3] >> http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 > > -- regards, Andrew Dinn ----------- Senior Principal Software Engineer Red Hat UK Ltd Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander From vladimir.kozlov at oracle.com Fri May 17 14:50:38 2019 From: vladimir.kozlov at oracle.com (Vladimir Kozlov) Date: Fri, 17 May 2019 07:50:38 -0700 Subject: New JDK Committer: Boris Ulasevich In-Reply-To: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> Message-ID: <54C3E9C1-E968-4F97-90CB-D5F7F80FF019@oracle.com> Vote yes Thanks Vladimir > On May 17, 2019, at 3:08 AM, Aleksey Shipilev wrote: > > I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. > > Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed > 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be > able to push the fixes without involving sponsors. > > Votes are due by June 1 12:00 CET. > > Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the > open by replying to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > -Aleksey Shipilev > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] > http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 > From vladimir.kozlov at oracle.com Fri May 17 14:51:45 2019 From: vladimir.kozlov at oracle.com (Vladimir Kozlov) Date: Fri, 17 May 2019 07:51:45 -0700 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: <69D618D4-05E2-46D8-9B92-FDF7B53895E8@oracle.com> Vote yes Thanks Vladimir > On May 17, 2019, at 1:09 AM, Doerr, Martin wrote: > > I hereby nominate Richard Reingruber (rrich) to JDK Committer. > > Richard is a long term member of the SAP JVM team with experience in various areas of hotspot like runtime, C1 and C2 compilers, garbage collection, debugging/JVMTI, s390 platform code. > > He already contributed 9 changes to OpenJDK [3] and he's working on further contributions. I think it's time to make him a Committer. > > Votes are due by May 31 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Martin Doerr > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=(author(%22rrich%22)%20or%20desc(%22Contributed-by%3A%20richard.reingruber%40sap.com%22))%20and%20not%20merge()&revcount=40 > From serguei.spitsyn at oracle.com Fri May 17 20:14:56 2019 From: serguei.spitsyn at oracle.com (serguei.spitsyn at oracle.com) Date: Fri, 17 May 2019 13:14:56 -0700 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: <05440aa7-0c5f-9460-ca00-589ddbeccb3a@oracle.com> Vote: yes From serguei.spitsyn at oracle.com Fri May 17 20:13:42 2019 From: serguei.spitsyn at oracle.com (serguei.spitsyn at oracle.com) Date: Fri, 17 May 2019 13:13:42 -0700 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: Vote: yes From dean.long at oracle.com Fri May 17 21:01:18 2019 From: dean.long at oracle.com (dean.long at oracle.com) Date: Fri, 17 May 2019 14:01:18 -0700 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: Vote: yes dl On 5/17/19 3:09 AM, Aleksey Shipilev wrote: > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > -Aleksey > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: >> I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. >> >> Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed >> 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be >> able to push the fixes without involving sponsors. >> >> Votes are due by June 1 12:00 CET. >> >> Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the >> open by replying to this mailing list. >> >> For Lazy Consensus voting instructions, see [2]. >> >> -Aleksey Shipilev >> >> [1] http://openjdk.java.net/census >> [2] http://openjdk.java.net/projects/#committer-vote >> [3] >> http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 From kim.barrett at oracle.com Sat May 18 00:49:39 2019 From: kim.barrett at oracle.com (Kim Barrett) Date: Fri, 17 May 2019 20:49:39 -0400 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: <80A60283-CF89-4C68-A4C4-2E7C4502EAA0@oracle.com> vote: yes On May 17, 2019, at 6:09 AM, Aleksey Shipilev wrote: > > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > -Aleksey > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: >> I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. >> >> Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed >> 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be >> able to push the fixes without involving sponsors. >> >> Votes are due by June 1 12:00 CET. >> >> Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the >> open by replying to this mailing list. >> >> For Lazy Consensus voting instructions, see [2]. >> >> -Aleksey Shipilev >> >> [1] http://openjdk.java.net/census >> [2] http://openjdk.java.net/projects/#committer-vote >> [3] >> http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 > From Sergey.Bylokhov at oracle.com Sat May 18 02:57:03 2019 From: Sergey.Bylokhov at oracle.com (Sergey Bylokhov) Date: Fri, 17 May 2019 19:57:03 -0700 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: <57f6b346-106b-2b57-2803-640081612d1a@oracle.com> Vote: yes -- Best regards, Sergey. From igor.ignatyev at oracle.com Sat May 18 03:09:42 2019 From: igor.ignatyev at oracle.com (Igor Ignatyev) Date: Fri, 17 May 2019 20:09:42 -0700 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: <5846B086-F3C1-43F7-879D-A2D938341B1E@oracle.com> Vote: yes -- Igor > On May 17, 2019, at 3:09 AM, Aleksey Shipilev wrote: > >> I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. From jianglizhou at google.com Sat May 18 03:18:29 2019 From: jianglizhou at google.com (Jiangli Zhou) Date: Fri, 17 May 2019 20:18:29 -0700 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: Vote: yes Best Regards, Jiangli On Fri, May 17, 2019 at 3:10 AM Aleksey Shipilev wrote: > > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > -Aleksey > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: > > I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. > > > > Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed > > 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be > > able to push the fixes without involving sponsors. > > > > Votes are due by June 1 12:00 CET. > > > > Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the > > open by replying to this mailing list. > > > > For Lazy Consensus voting instructions, see [2]. > > > > -Aleksey Shipilev > > > > [1] http://openjdk.java.net/census > > [2] http://openjdk.java.net/projects/#committer-vote > > [3] > > http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 > From dmitry.markov at oracle.com Sat May 18 08:13:43 2019 From: dmitry.markov at oracle.com (Dmitry Markov) Date: Sat, 18 May 2019 09:13:43 +0100 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: <4E392916-B5D1-461B-A5FF-BEEEB5C2146F@oracle.com> Vote: yes Thanks, Dmitry > On 17 May 2019, at 11:09, Aleksey Shipilev wrote: > > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > -Aleksey > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: >> I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. >> >> Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed >> 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be >> able to push the fixes without involving sponsors. >> >> Votes are due by June 1 12:00 CET. >> >> Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the >> open by replying to this mailing list. >> >> For Lazy Consensus voting instructions, see [2]. >> >> -Aleksey Shipilev >> >> [1] http://openjdk.java.net/census >> [2] http://openjdk.java.net/projects/#committer-vote >> [3] >> http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 > From christoph.langer at sap.com Mon May 20 07:09:35 2019 From: christoph.langer at sap.com (Langer, Christoph) Date: Mon, 20 May 2019 07:09:35 +0000 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: Vote: yes /Christoph > -----Original Message----- > From: jdk-dev On Behalf Of Doerr, > Martin > Sent: Freitag, 17. Mai 2019 10:10 > To: jdk-dev at openjdk.java.net > Subject: [CAUTION] CFV: New JDK Committer: Richard Reingruber > > I hereby nominate Richard Reingruber (rrich) to JDK Committer. > > Richard is a long term member of the SAP JVM team with experience in > various areas of hotspot like runtime, C1 and C2 compilers, garbage > collection, debugging/JVMTI, s390 platform code. > > He already contributed 9 changes to OpenJDK [3] and he's working on further > contributions. I think it's time to make him a Committer. > > Votes are due by May 31 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Martin Doerr > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] > http://hg.openjdk.java.net/jdk/jdk/search/?rev=(author(%22rrich%22)%20o > r%20desc(%22Contributed- > by%3A%20richard.reingruber%40sap.com%22))%20and%20not%20merge()& > revcount=40 From christoph.langer at sap.com Mon May 20 07:11:27 2019 From: christoph.langer at sap.com (Langer, Christoph) Date: Mon, 20 May 2019 07:11:27 +0000 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: Vote:yes /Christoph > -----Original Message----- > From: jdk-dev On Behalf Of Aleksey > Shipilev > Sent: Freitag, 17. Mai 2019 12:10 > To: jdk-dev at openjdk.java.net > Subject: CFV: New JDK Committer: Boris Ulasevich > > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > -Aleksey > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: > > I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. > > > > Boris is the member of BellSoft JVM team with experience in x86_32 and > ARM32. He already contributed > > 32 changes to OpenJDK [3] that improved the OpenJDK support on those > platforms, and he should be > > able to push the fixes without involving sponsors. > > > > Votes are due by June 1 12:00 CET. > > > > Only current JDK Committers [1] are eligible to vote on this nomination. > Votes must be cast in the > > open by replying to this mailing list. > > > > For Lazy Consensus voting instructions, see [2]. > > > > -Aleksey Shipilev > > > > [1] http://openjdk.java.net/census > > [2] http://openjdk.java.net/projects/#committer-vote > > [3] > > > http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevi > ch%22%29%20or%20desc%28%22boris.ulasevich%40bell- > sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 From robbin.ehn at oracle.com Mon May 20 08:25:44 2019 From: robbin.ehn at oracle.com (Robbin Ehn) Date: Mon, 20 May 2019 10:25:44 +0200 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: Vote: yes /Robbin On 2019-05-17 10:09, Doerr, Martin wrote: > I hereby nominate Richard Reingruber (rrich) to JDK Committer. > > Richard is a long term member of the SAP JVM team with experience in various areas of hotspot like runtime, C1 and C2 compilers, garbage collection, debugging/JVMTI, s390 platform code. > > He already contributed 9 changes to OpenJDK [3] and he's working on further contributions. I think it's time to make him a Committer. > > Votes are due by May 31 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Martin Doerr > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=(author(%22rrich%22)%20or%20desc(%22Contributed-by%3A%20richard.reingruber%40sap.com%22))%20and%20not%20merge()&revcount=40 > From vladimir.x.ivanov at oracle.com Mon May 20 10:31:01 2019 From: vladimir.x.ivanov at oracle.com (Vladimir Ivanov) Date: Mon, 20 May 2019 13:31:01 +0300 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: Vote: yes Best regards, Vladimir Ivanov On 17/05/2019 11:09, Doerr, Martin wrote: > I hereby nominate Richard Reingruber (rrich) to JDK Committer. From vladimir.x.ivanov at oracle.com Mon May 20 10:31:45 2019 From: vladimir.x.ivanov at oracle.com (Vladimir Ivanov) Date: Mon, 20 May 2019 13:31:45 +0300 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: <67f218bc-013b-fe92-b4b1-47af0f49fcaa@oracle.com> Vote: yes Best regards, Vladimir Ivanov On 17/05/2019 13:09, Aleksey Shipilev wrote: > I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. From dmitry.chuyko at bell-sw.com Mon May 20 10:37:31 2019 From: dmitry.chuyko at bell-sw.com (Dmitry Chuyko) Date: Mon, 20 May 2019 13:37:31 +0300 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: <664d5ffa-075e-eeab-d78a-cbb3305e3330@bell-sw.com> Vote: yes On 5/17/19 1:09 PM, Aleksey Shipilev wrote: > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > -Aleksey > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: >> I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. >> >> Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed >> 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be >> able to push the fixes without involving sponsors. >> >> Votes are due by June 1 12:00 CET. >> >> Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the >> open by replying to this mailing list. >> >> For Lazy Consensus voting instructions, see [2]. >> >> -Aleksey Shipilev >> >> [1] http://openjdk.java.net/census >> [2] http://openjdk.java.net/projects/#committer-vote >> [3] >> http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 From shade at redhat.com Mon May 20 14:28:23 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 20 May 2019 16:28:23 +0200 Subject: jdk-submit and unclosed branches Message-ID: Hi, It seems that the hygienic procedure for jdk-submit is to close branches after we are done with them. Stanislav, is that still a recommended practice? I have my batch of closes I can push. Anyhow, after trying to figure which branches belong to me, I realized maybe somebody else wants to close their own too. This is the one-liner to get the list of currently open branches with their last changesets: $ hg branches | awk '{ print $1; }' | xargs -n 1 hg log -l 1 -T "{author}\t{branch}\t{desc|firstline}\n" -b | sort -k 1,2 Sample report: http://cr.openjdk.java.net/~shade/scratch/sandbox-non-closed.txt Branch can be closed like this: $ hg up -r JDK-XXXXXXX $ hg commit --close-branch -m "Closing branch" Then check the outgoing commits (note the target branches) and push: $ hg out $ hg push -- Thanks, -Aleksey From coleen.phillimore at oracle.com Mon May 20 14:46:27 2019 From: coleen.phillimore at oracle.com (coleen.phillimore at oracle.com) Date: Mon, 20 May 2019 10:46:27 -0400 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: Vote: yes On 5/13/19 11:09 AM, Andrew Haley wrote: > I hereby nominate Severin Gehwolf to JDK Reviewer. > > Severin has contributed ~60 changesets[1] to OpenJDK since > 2015. Backporting work exceeds 10. This includes jdk11u and > jdk8u[2]. Some backports were non-trivial. He has filed 2 CSRs[3] so > far. > > Most contributions have been to hotspot/serviceability and build > areas. > > Recent, yet uncommitted, work will include more container work in the > JVM (cgroup v2) and a new jlink plugin. > > Specific changes worth mentioning: > > - Added Nestmates support to Zero (JEP-181)[4]. > - Improved container limits dection in the JVM[5]. > - Fixed a memory leak in the debugger[6]. > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [2] https://hg.openjdk.java.net/jdk8u/jdk8u/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/log?revcount=200&rev=(author(sgehwolf)+or+desc(%22sgehwolf at redhat.com%22))+and+not+merge() > [3] https://bugs.openjdk.java.net/issues/?filter=-2&jql=issuetype%20%3D%20CSR%20and%20assignee%20%3D%20sgehwolf%20ORDER%20BY%20created%20DESC > [4] https://hg.openjdk.java.net/jdk/jdk/rev/f703d45c5687 > [5] https://hg.openjdk.java.net/jdk/jdk/rev/1c242c2d037f > [6] https://hg.openjdk.java.net/jdk/jdk/rev/f7477110f0d7 > > > Votes are due by May 27, 2019. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > From coleen.phillimore at oracle.com Mon May 20 14:47:03 2019 From: coleen.phillimore at oracle.com (coleen.phillimore at oracle.com) Date: Mon, 20 May 2019 10:47:03 -0400 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: Vote: yes On 5/17/19 4:09 AM, Doerr, Martin wrote: > I hereby nominate Richard Reingruber (rrich) to JDK Committer. > > Richard is a long term member of the SAP JVM team with experience in various areas of hotspot like runtime, C1 and C2 compilers, garbage collection, debugging/JVMTI, s390 platform code. > > He already contributed 9 changes to OpenJDK [3] and he's working on further contributions. I think it's time to make him a Committer. > > Votes are due by May 31 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Martin Doerr > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=(author(%22rrich%22)%20or%20desc(%22Contributed-by%3A%20richard.reingruber%40sap.com%22))%20and%20not%20merge()&revcount=40 > From coleen.phillimore at oracle.com Mon May 20 14:47:14 2019 From: coleen.phillimore at oracle.com (coleen.phillimore at oracle.com) Date: Mon, 20 May 2019 10:47:14 -0400 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: Vote: yes On 5/17/19 6:09 AM, Aleksey Shipilev wrote: > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > -Aleksey > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: >> I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. >> >> Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed >> 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be >> able to push the fixes without involving sponsors. >> >> Votes are due by June 1 12:00 CET. >> >> Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the >> open by replying to this mailing list. >> >> For Lazy Consensus voting instructions, see [2]. >> >> -Aleksey Shipilev >> >> [1] http://openjdk.java.net/census >> [2] http://openjdk.java.net/projects/#committer-vote >> [3] >> http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 From zgu at redhat.com Mon May 20 14:51:00 2019 From: zgu at redhat.com (Zhengyu Gu) Date: Mon, 20 May 2019 10:51:00 -0400 Subject: New JDK Committer: Boris Ulasevich In-Reply-To: <54C3E9C1-E968-4F97-90CB-D5F7F80FF019@oracle.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <54C3E9C1-E968-4F97-90CB-D5F7F80FF019@oracle.com> Message-ID: Vote: yes -Zhengyu > >> On May 17, 2019, at 3:08 AM, Aleksey Shipilev wrote: >> >> I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. >> >> Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed >> 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be >> able to push the fixes without involving sponsors. >> >> Votes are due by June 1 12:00 CET. >> >> Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the >> open by replying to this mailing list. >> >> For Lazy Consensus voting instructions, see [2]. >> >> -Aleksey Shipilev >> >> [1] http://openjdk.java.net/census >> [2] http://openjdk.java.net/projects/#committer-vote >> [3] >> http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 >> > From roman at kennke.org Mon May 20 15:43:54 2019 From: roman at kennke.org (Roman Kennke) Date: Mon, 20 May 2019 17:43:54 +0200 Subject: jdk-submit and unclosed branches In-Reply-To: References: Message-ID: <1b939f33-1a75-4926-6896-17b7fa6380ed@kennke.org> Hi Aleksey, it's also documented here, and simpler: https://wiki.openjdk.java.net/display/Build/Submit+Repo#SubmitRepo-HowcanIseemyopenbranches? $ hg log -r "heads(all()) and not closed() and user('') and not branch(default)" Roman > Hi, > > It seems that the hygienic procedure for jdk-submit is to close branches after we are done with > them. Stanislav, is that still a recommended practice? I have my batch of closes I can push. > > Anyhow, after trying to figure which branches belong to me, I realized maybe somebody else wants to > close their own too. This is the one-liner to get the list of currently open branches with their > last changesets: > > $ hg branches | awk '{ print $1; }' | xargs -n 1 hg log -l 1 -T > "{author}\t{branch}\t{desc|firstline}\n" -b | sort -k 1,2 > > Sample report: > http://cr.openjdk.java.net/~shade/scratch/sandbox-non-closed.txt > > Branch can be closed like this: > > $ hg up -r JDK-XXXXXXX > $ hg commit --close-branch -m "Closing branch" > > Then check the outgoing commits (note the target branches) and push: > > $ hg out > $ hg push > From shade at redhat.com Mon May 20 15:45:30 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 20 May 2019 17:45:30 +0200 Subject: jdk-submit and unclosed branches In-Reply-To: <1b939f33-1a75-4926-6896-17b7fa6380ed@kennke.org> References: <1b939f33-1a75-4926-6896-17b7fa6380ed@kennke.org> Message-ID: On 5/20/19 5:43 PM, Roman Kennke wrote: > it's also documented here, and simpler: > > https://wiki.openjdk.java.net/display/Build/Submit+Repo#SubmitRepo-HowcanIseemyopenbranches? > > $ hg log -r "heads(all()) and not closed() and user('') and not > branch(default)" Right, thanks. -Aleksey From stanislav.smirnov at oracle.com Mon May 20 15:53:20 2019 From: stanislav.smirnov at oracle.com (Stanislav Smirnov) Date: Mon, 20 May 2019 11:53:20 -0400 Subject: jdk-submit and unclosed branches In-Reply-To: References: Message-ID: <12A60195-7504-4BC4-9640-A0FCAB930706@oracle.com> Hi Aleksey, yes, definitely this is something we expect from users. Best regards, Stanislav Smirnov > On May 20, 2019, at 10:28 AM, Aleksey Shipilev wrote: > > Hi, > > It seems that the hygienic procedure for jdk-submit is to close branches after we are done with > them. Stanislav, is that still a recommended practice? I have my batch of closes I can push. > > Anyhow, after trying to figure which branches belong to me, I realized maybe somebody else wants to > close their own too. This is the one-liner to get the list of currently open branches with their > last changesets: > > $ hg branches | awk '{ print $1; }' | xargs -n 1 hg log -l 1 -T > "{author}\t{branch}\t{desc|firstline}\n" -b | sort -k 1,2 > > Sample report: > http://cr.openjdk.java.net/~shade/scratch/sandbox-non-closed.txt > > Branch can be closed like this: > > $ hg up -r JDK-XXXXXXX > $ hg commit --close-branch -m "Closing branch" > > Then check the outgoing commits (note the target branches) and push: > > $ hg out > $ hg push > > -- > Thanks, > -Aleksey > > From jianglizhou at google.com Mon May 20 18:01:45 2019 From: jianglizhou at google.com (Jiangli Zhou) Date: Mon, 20 May 2019 11:01:45 -0700 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: Vote: yes Best regards, Jiangli On Fri, May 17, 2019 at 1:10 AM Doerr, Martin wrote: > > I hereby nominate Richard Reingruber (rrich) to JDK Committer. > > Richard is a long term member of the SAP JVM team with experience in various areas of hotspot like runtime, C1 and C2 compilers, garbage collection, debugging/JVMTI, s390 platform code. > > He already contributed 9 changes to OpenJDK [3] and he's working on further contributions. I think it's time to make him a Committer. > > Votes are due by May 31 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Martin Doerr > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=(author(%22rrich%22)%20or%20desc(%22Contributed-by%3A%20richard.reingruber%40sap.com%22))%20and%20not%20merge()&revcount=40 > From jianglizhou at google.com Mon May 20 18:12:29 2019 From: jianglizhou at google.com (Jiangli Zhou) Date: Mon, 20 May 2019 11:12:29 -0700 Subject: CFV: New JDK Committer: Arthur Eubanks Message-ID: I hereby nominate Arthur Eubanks (aeubanks) to JDK committer. Arthur is a member of the Java team at Google and has contributed 15 changesets [3] in OpenJDK. His has contributed changes for supporting Clang on Linux and making JDK work in IPv6-only environments. He is also actively contributing to the Java TSAN project [4] [5]. Votes are due by June 3, 2019. Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. For Lazy Consensus voting instructions, see [2]. [1] http://openjdk.java.net/census [2] http://openjdk.java.net/projects/#committer-vote [3] http://hg.openjdk.java.net/jdk/jdk/log?revcount=20&rev=%28author%28%22aeubanks%22%29+or+desc%28%22Contributed-by%3A+aeubanks%40google.com%22%29%29+or+desc%28%22Contributed-by%3A+Arthur+Eubanks+%3Caeubanks%40google.com%3E%22%29+and+not+merge%28%29 [4] https://openjdk.java.net/projects/tsan/ [5] https://hg.openjdk.java.net/tsan/dev/ Regards, Jiangli From jianglizhou at google.com Mon May 20 18:13:55 2019 From: jianglizhou at google.com (Jiangli Zhou) Date: Mon, 20 May 2019 11:13:55 -0700 Subject: CFV: New JDK Committer: Arthur Eubanks In-Reply-To: References: Message-ID: Vote: yes Regards, Jiangli On Mon, May 20, 2019 at 11:12 AM Jiangli Zhou wrote: > > I hereby nominate Arthur Eubanks (aeubanks) to JDK committer. > > Arthur is a member of the Java team at Google and has contributed 15 > changesets [3] in OpenJDK. His has contributed changes for supporting > Clang on Linux and making JDK work in IPv6-only environments. He is > also actively contributing to the Java TSAN project [4] [5]. > > Votes are due by June 3, 2019. > > Only current JDK Committers [1] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this mailing > list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/log?revcount=20&rev=%28author%28%22aeubanks%22%29+or+desc%28%22Contributed-by%3A+aeubanks%40google.com%22%29%29+or+desc%28%22Contributed-by%3A+Arthur+Eubanks+%3Caeubanks%40google.com%3E%22%29+and+not+merge%28%29 > [4] https://openjdk.java.net/projects/tsan/ > [5] https://hg.openjdk.java.net/tsan/dev/ > > Regards, > Jiangli From martinrb at google.com Mon May 20 18:19:11 2019 From: martinrb at google.com (Martin Buchholz) Date: Mon, 20 May 2019 11:19:11 -0700 Subject: CFV: New JDK Committer: Arthur Eubanks In-Reply-To: References: Message-ID: Vote: yes On Mon, May 20, 2019 at 11:13 AM Jiangli Zhou wrote: > I hereby nominate Arthur Eubanks (aeubanks) to JDK committer. > > Arthur is a member of the Java team at Google and has contributed 15 > changesets [3] in OpenJDK. His has contributed changes for supporting > Clang on Linux and making JDK work in IPv6-only environments. He is > also actively contributing to the Java TSAN project [4] [5]. > > Votes are due by June 3, 2019. > > Only current JDK Committers [1] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this mailing > list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] > http://hg.openjdk.java.net/jdk/jdk/log?revcount=20&rev=%28author%28%22aeubanks%22%29+or+desc%28%22Contributed-by%3A+aeubanks%40google.com%22%29%29+or+desc%28%22Contributed-by%3A+Arthur+Eubanks+%3Caeubanks%40google.com%3E%22%29+and+not+merge%28%29 > [4] https://openjdk.java.net/projects/tsan/ > [5] https://hg.openjdk.java.net/tsan/dev/ > > Regards, > Jiangli > From daniel.fuchs at oracle.com Mon May 20 18:23:20 2019 From: daniel.fuchs at oracle.com (Daniel Fuchs) Date: Mon, 20 May 2019 19:23:20 +0100 Subject: CFV: New JDK Committer: Arthur Eubanks In-Reply-To: References: Message-ID: <91d40df9-d351-fe75-cf55-3e6ac90d5ee0@oracle.com> Vote: yes best regards, -- daniel On 20/05/2019 19:12, Jiangli Zhou wrote: > I hereby nominate Arthur Eubanks (aeubanks) to JDK committer. From sgehwolf at redhat.com Mon May 20 18:28:18 2019 From: sgehwolf at redhat.com (Severin Gehwolf) Date: Mon, 20 May 2019 20:28:18 +0200 Subject: CFV: New JDK Committer: Arthur Eubanks In-Reply-To: References: Message-ID: <02df724a841e5887c90840efce43338099bee41a.camel@redhat.com> Vote: yes On Mon, 2019-05-20 at 11:12 -0700, Jiangli Zhou wrote: > I hereby nominate Arthur Eubanks (aeubanks) to JDK committer. From manc at google.com Mon May 20 18:28:29 2019 From: manc at google.com (Man Cao) Date: Mon, 20 May 2019 11:28:29 -0700 Subject: CFV: New JDK Committer: Arthur Eubanks In-Reply-To: References: Message-ID: Vote: yes -Man On Mon, May 20, 2019 at 11:13 AM Jiangli Zhou wrote: > I hereby nominate Arthur Eubanks (aeubanks) to JDK committer. > > Arthur is a member of the Java team at Google and has contributed 15 > changesets [3] in OpenJDK. His has contributed changes for supporting > Clang on Linux and making JDK work in IPv6-only environments. He is > also actively contributing to the Java TSAN project [4] [5]. > > Votes are due by June 3, 2019. > > Only current JDK Committers [1] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this mailing > list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] > http://hg.openjdk.java.net/jdk/jdk/log?revcount=20&rev=%28author%28%22aeubanks%22%29+or+desc%28%22Contributed-by%3A+aeubanks%40google.com%22%29%29+or+desc%28%22Contributed-by%3A+Arthur+Eubanks+%3Caeubanks%40google.com%3E%22%29+and+not+merge%28%29 > [4] https://openjdk.java.net/projects/tsan/ > [5] https://hg.openjdk.java.net/tsan/dev/ > > Regards, > Jiangli > From andy.herrick at oracle.com Mon May 20 18:39:37 2019 From: andy.herrick at oracle.com (Andy Herrick) Date: Mon, 20 May 2019 14:39:37 -0400 Subject: CFV: New JDK Committer: Arthur Eubanks In-Reply-To: References: Message-ID: <2ad5959f-8fbf-fad5-72b0-2b980eb03bb6@oracle.com> vote: yes On 5/20/2019 2:12 PM, Jiangli Zhou wrote: > I hereby nominate Arthur Eubanks (aeubanks) to JDK committer. > > Arthur is a member of the Java team at Google and has contributed 15 > changesets [3] in OpenJDK. His has contributed changes for supporting > Clang on Linux and making JDK work in IPv6-only environments. He is > also actively contributing to the Java TSAN project [4] [5]. > > Votes are due by June 3, 2019. > > Only current JDK Committers [1] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this mailing > list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/log?revcount=20&rev=%28author%28%22aeubanks%22%29+or+desc%28%22Contributed-by%3A+aeubanks%40google.com%22%29%29+or+desc%28%22Contributed-by%3A+Arthur+Eubanks+%3Caeubanks%40google.com%3E%22%29+and+not+merge%28%29 > [4] https://openjdk.java.net/projects/tsan/ > [5] https://hg.openjdk.java.net/tsan/dev/ > > Regards, > Jiangli From chris.hegarty at oracle.com Mon May 20 19:18:32 2019 From: chris.hegarty at oracle.com (Chris Hegarty) Date: Mon, 20 May 2019 20:18:32 +0100 Subject: CFV: New JDK Committer: Arthur Eubanks In-Reply-To: References: Message-ID: <8677AA20-D604-4A66-A383-2BF20E8ACEE7@oracle.com> Vote: YES -Chris > On 20 May 2019, at 19:13, Jiangli Zhou wrote: > > Vote: yes > > Regards, > Jiangli > >> On Mon, May 20, 2019 at 11:12 AM Jiangli Zhou wrote: >> >> I hereby nominate Arthur Eubanks (aeubanks) to JDK committer. >> >> Arthur is a member of the Java team at Google and has contributed 15 >> changesets [3] in OpenJDK. His has contributed changes for supporting >> Clang on Linux and making JDK work in IPv6-only environments. He is >> also actively contributing to the Java TSAN project [4] [5]. >> >> Votes are due by June 3, 2019. >> >> Only current JDK Committers [1] are eligible to vote on this >> nomination. Votes must be cast in the open by replying to this mailing >> list. >> >> For Lazy Consensus voting instructions, see [2]. >> >> [1] http://openjdk.java.net/census >> [2] http://openjdk.java.net/projects/#committer-vote >> [3] http://hg.openjdk.java.net/jdk/jdk/log?revcount=20&rev=%28author%28%22aeubanks%22%29+or+desc%28%22Contributed-by%3A+aeubanks%40google.com%22%29%29+or+desc%28%22Contributed-by%3A+Arthur+Eubanks+%3Caeubanks%40google.com%3E%22%29+and+not+merge%28%29 >> [4] https://openjdk.java.net/projects/tsan/ >> [5] https://hg.openjdk.java.net/tsan/dev/ >> >> Regards, >> Jiangli From rasbold at google.com Mon May 20 20:19:49 2019 From: rasbold at google.com (Chuck Rasbold) Date: Mon, 20 May 2019 13:19:49 -0700 Subject: CFV: New JDK Committer: Arthur Eubanks In-Reply-To: References: Message-ID: Vote: yes On Mon, May 20, 2019 at 11:13 AM Jiangli Zhou wrote: > I hereby nominate Arthur Eubanks (aeubanks) to JDK committer. > > Arthur is a member of the Java team at Google and has contributed 15 > changesets [3] in OpenJDK. His has contributed changes for supporting > Clang on Linux and making JDK work in IPv6-only environments. He is > also actively contributing to the Java TSAN project [4] [5]. > > Votes are due by June 3, 2019. > > Only current JDK Committers [1] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this mailing > list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] > http://hg.openjdk.java.net/jdk/jdk/log?revcount=20&rev=%28author%28%22aeubanks%22%29+or+desc%28%22Contributed-by%3A+aeubanks%40google.com%22%29%29+or+desc%28%22Contributed-by%3A+Arthur+Eubanks+%3Caeubanks%40google.com%3E%22%29+and+not+merge%28%29 > [4] https://openjdk.java.net/projects/tsan/ > [5] https://hg.openjdk.java.net/tsan/dev/ > > Regards, > Jiangli > From gromero at linux.vnet.ibm.com Mon May 20 22:48:59 2019 From: gromero at linux.vnet.ibm.com (Gustavo Romero) Date: Mon, 20 May 2019 19:48:59 -0300 Subject: CFV: New JDK Committer: Richard Reingruber In-Reply-To: References: Message-ID: <46109df0-7a34-6429-46e2-bb923e1b402b@linux.vnet.ibm.com> Vote: yes Best regards, Gustavo On 05/17/2019 05:09 AM, Doerr, Martin wrote: > I hereby nominate Richard Reingruber (rrich) to JDK Committer. > > Richard is a long term member of the SAP JVM team with experience in various areas of hotspot like runtime, C1 and C2 compilers, garbage collection, debugging/JVMTI, s390 platform code. > > He already contributed 9 changes to OpenJDK [3] and he's working on further contributions. I think it's time to make him a Committer. > > Votes are due by May 31 12:00 CET. > > Only current JDK Committers [1] are eligible to vote > on this nomination. Votes must be cast in the open by replying > to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Martin Doerr > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=(author(%22rrich%22)%20or%20desc(%22Contributed-by%3A%20richard.reingruber%40sap.com%22))%20and%20not%20merge()&revcount=40 > From gromero at linux.vnet.ibm.com Mon May 20 22:52:57 2019 From: gromero at linux.vnet.ibm.com (Gustavo Romero) Date: Mon, 20 May 2019 19:52:57 -0300 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: <85b40378-39d9-0f84-3c07-3e9a9835baa4@linux.vnet.ibm.com> Vote: yes Best regards, Gustavo On 05/17/2019 07:09 AM, Aleksey Shipilev wrote: > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > -Aleksey > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: >> I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. >> >> Boris is the member of BellSoft JVM team with experience in x86_32 and ARM32. He already contributed >> 32 changes to OpenJDK [3] that improved the OpenJDK support on those platforms, and he should be >> able to push the fixes without involving sponsors. >> >> Votes are due by June 1 12:00 CET. >> >> Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the >> open by replying to this mailing list. >> >> For Lazy Consensus voting instructions, see [2]. >> >> -Aleksey Shipilev >> >> [1] http://openjdk.java.net/census >> [2] http://openjdk.java.net/projects/#committer-vote >> [3] >> http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevich%22%29%20or%20desc%28%22boris.ulasevich%40bell-sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 > From serguei.spitsyn at oracle.com Tue May 21 00:07:50 2019 From: serguei.spitsyn at oracle.com (serguei.spitsyn at oracle.com) Date: Mon, 20 May 2019 17:07:50 -0700 Subject: CFV: New JDK Committer: Arthur Eubanks In-Reply-To: References: Message-ID: Vote: yes From david.holmes at oracle.com Tue May 21 02:03:17 2019 From: david.holmes at oracle.com (David Holmes) Date: Tue, 21 May 2019 12:03:17 +1000 Subject: CFV: New JDK Committer: Ralf Schmelter In-Reply-To: References: Message-ID: Vote: yes David On 10/05/2019 5:51 pm, Langer, Christoph wrote: > I hereby nominate Ralf Schmelter (rschmelter) to JDK Project Committer. > > Ralf is a long term member of the SAP JVM team with experience in various areas such as hotspot, garbage collection, debugging/JVMTI and many more. > > He started contributing to OpenJDK quite recently and has already piled up 13 changesets [3]. I think it's about time to make him a Committer. > > Votes are due by May 24 12:00 CET. > > Only current JDK Committers [1] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > > For Lazy Consensus voting instructions, see [2]. > > Christoph Langer > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22rschmelter%22%29%20or%20desc%28%22Contributed-by%3A%20ralf.schmelter%40sap.com%22%29%29%20and%20not%20merge%28%29&revcount=40 > From thomas.stuefe at gmail.com Tue May 21 03:19:59 2019 From: thomas.stuefe at gmail.com (=?UTF-8?Q?Thomas_St=C3=BCfe?=) Date: Tue, 21 May 2019 05:19:59 +0200 Subject: CFV: New JDK Committer: Arthur Eubanks In-Reply-To: References: Message-ID: Vote: yes On Mon, May 20, 2019, 20:13 Jiangli Zhou wrote: > I hereby nominate Arthur Eubanks (aeubanks) to JDK committer. > > Arthur is a member of the Java team at Google and has contributed 15 > changesets [3] in OpenJDK. His has contributed changes for supporting > Clang on Linux and making JDK work in IPv6-only environments. He is > also actively contributing to the Java TSAN project [4] [5]. > > Votes are due by June 3, 2019. > > Only current JDK Committers [1] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this mailing > list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] > http://hg.openjdk.java.net/jdk/jdk/log?revcount=20&rev=%28author%28%22aeubanks%22%29+or+desc%28%22Contributed-by%3A+aeubanks%40google.com%22%29%29+or+desc%28%22Contributed-by%3A+Arthur+Eubanks+%3Caeubanks%40google.com%3E%22%29+and+not+merge%28%29 > [4] https://openjdk.java.net/projects/tsan/ > [5] https://hg.openjdk.java.net/tsan/dev/ > > Regards, > Jiangli > From christoph.langer at sap.com Tue May 21 06:40:34 2019 From: christoph.langer at sap.com (Langer, Christoph) Date: Tue, 21 May 2019 06:40:34 +0000 Subject: CFV: New JDK Committer: Arthur Eubanks In-Reply-To: References: Message-ID: Vote:yes /Christoph > -----Original Message----- > From: jdk-dev On Behalf Of Jiangli > Zhou > Sent: Montag, 20. Mai 2019 20:12 > To: jdk-dev > Subject: CFV: New JDK Committer: Arthur Eubanks > > I hereby nominate Arthur Eubanks (aeubanks) to JDK committer. > > Arthur is a member of the Java team at Google and has contributed 15 > changesets [3] in OpenJDK. His has contributed changes for supporting > Clang on Linux and making JDK work in IPv6-only environments. He is > also actively contributing to the Java TSAN project [4] [5]. > > Votes are due by June 3, 2019. > > Only current JDK Committers [1] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this mailing > list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] > http://hg.openjdk.java.net/jdk/jdk/log?revcount=20&rev=%28author%28% > 22aeubanks%22%29+or+desc%28%22Contributed- > by%3A+aeubanks%40google.com%22%29%29+or+desc%28%22Contributed- > by%3A+Arthur+Eubanks+%3Caeubanks%40google.com%3E%22%29+and+no > t+merge%28%29 > [4] https://openjdk.java.net/projects/tsan/ > [5] https://hg.openjdk.java.net/tsan/dev/ > > Regards, > Jiangli From adinn at redhat.com Tue May 21 07:45:50 2019 From: adinn at redhat.com (Andrew Dinn) Date: Tue, 21 May 2019 08:45:50 +0100 Subject: CFV: New JDK Committer: Arthur Eubanks In-Reply-To: References: Message-ID: <924ad8fd-f488-3a7f-b05d-b6d77a13dbc2@redhat.com> Vote: yes On 20/05/2019 19:12, Jiangli Zhou wrote: > I hereby nominate Arthur Eubanks (aeubanks) to JDK committer. > > Arthur is a member of the Java team at Google and has contributed 15 > changesets [3] in OpenJDK. His has contributed changes for supporting > Clang on Linux and making JDK work in IPv6-only environments. He is > also actively contributing to the Java TSAN project [4] [5]. > > Votes are due by June 3, 2019. > > Only current JDK Committers [1] are eligible to vote on this > nomination. Votes must be cast in the open by replying to this mailing > list. > > For Lazy Consensus voting instructions, see [2]. > > [1] http://openjdk.java.net/census > [2] http://openjdk.java.net/projects/#committer-vote > [3] http://hg.openjdk.java.net/jdk/jdk/log?revcount=20&rev=%28author%28%22aeubanks%22%29+or+desc%28%22Contributed-by%3A+aeubanks%40google.com%22%29%29+or+desc%28%22Contributed-by%3A+Arthur+Eubanks+%3Caeubanks%40google.com%3E%22%29+and+not+merge%28%29 > [4] https://openjdk.java.net/projects/tsan/ > [5] https://hg.openjdk.java.net/tsan/dev/ > > Regards, > Jiangli > -- regards, Andrew Dinn ----------- Senior Principal Software Engineer Red Hat UK Ltd Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander From daniel.fuchs at oracle.com Tue May 21 09:07:23 2019 From: daniel.fuchs at oracle.com (Daniel Fuchs) Date: Tue, 21 May 2019 10:07:23 +0100 Subject: New JDK Committer: Boris Ulasevich In-Reply-To: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> Message-ID: <2494b190-c2ae-8e2e-179f-8967075fa681@oracle.com> Vote: Yes best regards, -- daniel On 17/05/2019 11:08, Aleksey Shipilev wrote: > I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. From devnexen at gmail.com Tue May 21 09:32:32 2019 From: devnexen at gmail.com (David CARLIER) Date: Tue, 21 May 2019 09:32:32 +0000 Subject: [PATCH]: pd_print_cpu_info/bsd display minimal info Message-ID: Hi, here a little patch proposal to improve slightly the BSD support. Thanks. Kind regards. -------------- next part -------------- A non-text attachment was scrubbed... Name: patch-src-hotspot-os-bsd-os_bsd_cpp.diff Type: text/x-patch Size: 882 bytes Desc: not available URL: From vladimir.x.ivanov at oracle.com Tue May 21 11:19:25 2019 From: vladimir.x.ivanov at oracle.com (Vladimir Ivanov) Date: Tue, 21 May 2019 14:19:25 +0300 Subject: CFV: New JDK Committer: Arthur Eubanks In-Reply-To: References: Message-ID: <64e0ac8d-f890-3b2f-0f26-adda247f079d@oracle.com> Vote: yes Best regards, Vladimir Ivanov On 20/05/2019 21:12, Jiangli Zhou wrote: > I hereby nominate Arthur Eubanks (aeubanks) to JDK committer. From vladimir.x.ivanov at oracle.com Tue May 21 11:23:32 2019 From: vladimir.x.ivanov at oracle.com (Vladimir Ivanov) Date: Tue, 21 May 2019 14:23:32 +0300 Subject: CFV: New JDK Committer: Ralf Schmelter In-Reply-To: References: Message-ID: <57cfa2a4-e432-0104-48a2-1fba3dfda87d@oracle.com> Vote: yes Best regards, Vladimir Ivanov On 10/05/2019 10:51, Langer, Christoph wrote: > I hereby nominate Ralf Schmelter (rschmelter) to JDK Project Committer. From vladimir.x.ivanov at oracle.com Tue May 21 11:24:17 2019 From: vladimir.x.ivanov at oracle.com (Vladimir Ivanov) Date: Tue, 21 May 2019 14:24:17 +0300 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: <654a9b53-7519-6f24-83a2-b83e8923453f@oracle.com> Vote: yes Best regards, Vladimir Ivanov On 13/05/2019 18:09, Andrew Haley wrote: > I hereby nominate Severin Gehwolf to JDK Reviewer. From derekw at marvell.com Tue May 21 15:39:30 2019 From: derekw at marvell.com (Derek White) Date: Tue, 21 May 2019 15:39:30 +0000 Subject: CFV: New JDK Committer: Boris Ulasevich In-Reply-To: References: <8cf718d4-d45d-1ad9-5b00-96184d97c2b2@redhat.com> <8d9228bb-b619-2c83-1a23-9156b5039dff@redhat.com> Message-ID: Vote: yes > -----Original Message----- > From: jdk-dev On Behalf Of Langer, > Christoph > Sent: Monday, May 20, 2019 3:11 AM > To: Aleksey Shipilev ; jdk-dev at openjdk.java.net > Subject: [EXT] RE: CFV: New JDK Committer: Boris Ulasevich > > External Email > > ---------------------------------------------------------------------- > Vote:yes > > /Christoph > > > -----Original Message----- > > From: jdk-dev On Behalf Of Aleksey > > Shipilev > > Sent: Freitag, 17. Mai 2019 12:10 > > To: jdk-dev at openjdk.java.net > > Subject: CFV: New JDK Committer: Boris Ulasevich > > > > Dang, missed "CFV: " from the subject, corrected. Please reply to this one. > > > > -Aleksey > > > > On 5/17/19 12:08 PM, Aleksey Shipilev wrote: > > > I hereby nominate Boris Ulasevich (bulasevich) to JDK Committer. > > > > > > Boris is the member of BellSoft JVM team with experience in x86_32 > > > and > > ARM32. He already contributed > > > 32 changes to OpenJDK [3] that improved the OpenJDK support on those > > platforms, and he should be > > > able to push the fixes without involving sponsors. > > > > > > Votes are due by June 1 12:00 CET. > > > > > > Only current JDK Committers [1] are eligible to vote on this nomination. > > Votes must be cast in the > > > open by replying to this mailing list. > > > > > > For Lazy Consensus voting instructions, see [2]. > > > > > > -Aleksey Shipilev > > > > > > [1] http://openjdk.java.net/census > > > [2] http://openjdk.java.net/projects/#committer-vote > > > [3] > > > > > > http://hg.openjdk.java.net/jdk/jdk/search/?rev=%28author%28%22bulasevi > > ch%22%29%20or%20desc%28%22boris.ulasevich%40bell- > > sw.com%22%29%29%20and%20not%20merge%28%29&revcount=100 From jcbeyler at google.com Wed May 22 02:47:25 2019 From: jcbeyler at google.com (Jean Christophe Beyler) Date: Tue, 21 May 2019 19:47:25 -0700 Subject: CFV: New JDK Committer: Arthur Eubanks In-Reply-To: <64e0ac8d-f890-3b2f-0f26-adda247f079d@oracle.com> References: <64e0ac8d-f890-3b2f-0f26-adda247f079d@oracle.com> Message-ID: Vote: yes Jc On Tue, May 21, 2019 at 4:20 AM Vladimir Ivanov < vladimir.x.ivanov at oracle.com> wrote: > Vote: yes > > Best regards, > Vladimir Ivanov > > On 20/05/2019 21:12, Jiangli Zhou wrote: > > I hereby nominate Arthur Eubanks (aeubanks) to JDK committer. > -- Thanks, Jc From Roger.Riggs at oracle.com Wed May 22 19:32:41 2019 From: Roger.Riggs at oracle.com (Roger Riggs) Date: Wed, 22 May 2019 15:32:41 -0400 Subject: CFV: New JDK Reviewer: Matthias Baesken In-Reply-To: References: Message-ID: Vote: Yes On 05/09/2019 04:07 AM, Volker Simonis wrote: > I hereby nominate Matthias Baesken (mbaesken) to JDK Project Reviewer. > From Roger.Riggs at oracle.com Wed May 22 19:34:07 2019 From: Roger.Riggs at oracle.com (Roger Riggs) Date: Wed, 22 May 2019 15:34:07 -0400 Subject: CFV: New JDK Reviewer: Severin Gehwolf In-Reply-To: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> References: <70249e0a-c2c7-04ca-ea92-6880f6f17544@redhat.com> Message-ID: Vote: Yes On 05/13/2019 11:09 AM, Andrew Haley wrote: > I hereby nominate Severin Gehwolf to JDK Reviewer. From joe.darcy at oracle.com Wed May 22 20:16:21 2019 From: joe.darcy at oracle.com (Joe Darcy) Date: Wed, 22 May 2019 13:16:21 -0700 Subject: Reminder: Rampdown Phase One of JDK 13 approaching on June 13, 2019, please factor in review time for CSRs Message-ID: Hello, As a reminder, per the JDK 13 schedule ??? http://openjdk.java.net/projects/jdk/13/ its Rampdown Phase One is approaching on June 13, 2019. If you have outstanding work for JDK 13 which requires CSR review (API spec changes, new command line options, etc.) please factor in CSR review time into your planning. More detail about the CSR process is written up on its wiki: ??? https://wiki.openjdk.java.net/display/csr/Main Cheers, -Joe From jesper.wilhelmsson at oracle.com Fri May 24 00:44:54 2019 From: jesper.wilhelmsson at oracle.com (jesper.wilhelmsson at oracle.com) Date: Fri, 24 May 2019 02:44:54 +0200 Subject: CFV: New JDK Reviewer: Mikael Vidstedt Message-ID: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. Votes are due by June 6, 2019. Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. For Lazy Consensus voting instructions, see [3]. Thanks, /Jesper [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() [2] http://openjdk.java.net/census [3] http://openjdk.java.net/projects/#project-reviewer From brian.burkhalter at oracle.com Fri May 24 00:47:08 2019 From: brian.burkhalter at oracle.com (Brian Burkhalter) Date: Thu, 23 May 2019 17:47:08 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <489BAF85-192D-423C-9E33-418B6304BC46@oracle.com> Vote: yes! > On May 23, 2019, at 5:44 PM, jesper.wilhelmsson at oracle.com wrote: > > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. From joe.darcy at oracle.com Fri May 24 00:48:44 2019 From: joe.darcy at oracle.com (Joseph D. Darcy) Date: Thu, 23 May 2019 17:48:44 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <5CE73F6C.40909@oracle.com> Vote: yes. -Joe On 5/23/2019 5:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From jianglizhou at google.com Fri May 24 00:50:56 2019 From: jianglizhou at google.com (Jiangli Zhou) Date: Thu, 23 May 2019 17:50:56 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: yes Best regards, Jiangli On Thu, May 23, 2019 at 5:45 PM wrote: > > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From james.laskey at oracle.com Fri May 24 00:54:15 2019 From: james.laskey at oracle.com (James Laskey) Date: Thu, 23 May 2019 21:54:15 -0300 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <215C5E20-DE3C-477F-B208-54C0E22AB858@oracle.com> Vote: yes Sent from my iPhone > On May 23, 2019, at 9:44 PM, jesper.wilhelmsson at oracle.com wrote: > > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From paul.hohensee at gmail.com Fri May 24 00:59:26 2019 From: paul.hohensee at gmail.com (Paul Hohensee) Date: Thu, 23 May 2019 17:59:26 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <215C5E20-DE3C-477F-B208-54C0E22AB858@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> <215C5E20-DE3C-477F-B208-54C0E22AB858@oracle.com> Message-ID: Vote: yes On Thu, May 23, 2019 at 5:56 PM James Laskey wrote: > Vote: yes > > Sent from my iPhone > > > On May 23, 2019, at 9:44 PM, jesper.wilhelmsson at oracle.com wrote: > > > > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, > mainly in the HotSpot and build areas, starting back in 2012. Mikael is > also the project lead for the Portola project. How he has escaped becoming > a Reviewer until now is a mystery. > > > > Votes are due by June 6, 2019. > > > > Only current JDK Reviewers [2] are eligible to vote on this nomination. > Votes must be cast in the open by replying to this mailing list. > > For Lazy Consensus voting instructions, see [3]. > > > > Thanks, > > /Jesper > > > > [1] > https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > > [2] http://openjdk.java.net/census > > [3] http://openjdk.java.net/projects/#project-reviewer > > > > From martinrb at google.com Fri May 24 01:08:57 2019 From: martinrb at google.com (Martin Buchholz) Date: Thu, 23 May 2019 18:08:57 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: yes On Thu, May 23, 2019 at 5:45 PM wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, > mainly in the HotSpot and build areas, starting back in 2012. Mikael is > also the project lead for the Portola project. How he has escaped becoming > a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. > Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] > https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > > From daniel.daugherty at oracle.com Fri May 24 01:10:16 2019 From: daniel.daugherty at oracle.com (Daniel D. Daugherty) Date: Thu, 23 May 2019 21:10:16 -0400 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <2ab5293f-9a38-7e09-26c4-2d558535d457@oracle.com> Vote: yes Dan On 5/23/19 8:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > > From philip.race at oracle.com Fri May 24 01:28:24 2019 From: philip.race at oracle.com (Philip Race) Date: Thu, 23 May 2019 18:28:24 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <5CE748B8.4020104@oracle.com> Vote: yes -phil. From brent.christian at oracle.com Fri May 24 01:31:06 2019 From: brent.christian at oracle.com (Brent Christian) Date: Thu, 23 May 2019 18:31:06 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: Yes -Brent On 5/23/19 5:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > From iris.clark at oracle.com Fri May 24 01:35:57 2019 From: iris.clark at oracle.com (Iris Clark) Date: Fri, 24 May 2019 01:35:57 +0000 (UTC) Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: yes Iris From igor.ignatyev at oracle.com Fri May 24 01:40:19 2019 From: igor.ignatyev at oracle.com (Igor Ignatyev) Date: Thu, 23 May 2019 18:40:19 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: As far as I remember, Mikael has his own reasons not to become a Reviewer and r privately ejected several offers to nominate him. I don't think it's enough to veto his nomination, however to respect his choice, I abstain from this voting. Vote: abstain -- Igor > On May 23, 2019, at 5:44 PM, jesper.wilhelmsson at oracle.com wrote: > > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From vicente.romero at oracle.com Fri May 24 01:41:03 2019 From: vicente.romero at oracle.com (Vicente Romero) Date: Thu, 23 May 2019 21:41:03 -0400 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <22356be5-ad35-a5ce-7bf0-c1cdd57eb0c7@oracle.com> vote: yes, Vicente On 5/23/19 8:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From Sergey.Bylokhov at oracle.com Fri May 24 02:04:02 2019 From: Sergey.Bylokhov at oracle.com (Sergey Bylokhov) Date: Thu, 23 May 2019 19:04:02 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <70b3afcc-116a-0c94-d9e8-7a8ad03fec73@oracle.com> Vote: yes -- Best regards, Sergey. From naoto.sato at oracle.com Fri May 24 02:13:08 2019 From: naoto.sato at oracle.com (naoto.sato at oracle.com) Date: Thu, 23 May 2019 19:13:08 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: yes Naoto On 5/23/19 5:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From ivan.gerasimov at oracle.com Fri May 24 02:28:00 2019 From: ivan.gerasimov at oracle.com (Ivan Gerasimov) Date: Thu, 23 May 2019 19:28:00 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <15651d53-46ec-c6ee-de6a-e27b8ea0bafb@oracle.com> Vote: Yes On 5/23/19 5:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. -- With kind regards, Ivan Gerasimov From thomas.stuefe at gmail.com Fri May 24 03:28:01 2019 From: thomas.stuefe at gmail.com (=?UTF-8?Q?Thomas_St=C3=BCfe?=) Date: Fri, 24 May 2019 05:28:01 +0200 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: yes On Fri, May 24, 2019, 02:45 wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, > mainly in the HotSpot and build areas, starting back in 2012. Mikael is > also the project lead for the Portola project. How he has escaped becoming > a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. > Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] > https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > > From chris.plummer at oracle.com Fri May 24 03:31:45 2019 From: chris.plummer at oracle.com (Chris Plummer) Date: Thu, 23 May 2019 20:31:45 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <5318fa95-24b9-5856-f589-abf63d21e161@oracle.com> vote: yes On 5/23/19 5:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From rasbold at google.com Fri May 24 04:12:14 2019 From: rasbold at google.com (Chuck Rasbold) Date: Thu, 23 May 2019 21:12:14 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: yes On Thu, May 23, 2019 at 5:45 PM wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, > mainly in the HotSpot and build areas, starting back in 2012. Mikael is > also the project lead for the Portola project. How he has escaped becoming > a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. > Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] > https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > > From jonathan.gibbons at oracle.com Fri May 24 04:34:36 2019 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Thu, 23 May 2019 21:34:36 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <8412a571-c12d-c55e-de36-60b5519e5073@oracle.com> Vote: yes On 5/23/19 5:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From john.r.rose at oracle.com Fri May 24 05:28:51 2019 From: john.r.rose at oracle.com (John Rose) Date: Thu, 23 May 2019 22:28:51 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <3A10467A-0864-47FA-B03F-65DC06B86BF5@oracle.com> Vote: yes From volker.simonis at gmail.com Fri May 24 06:12:53 2019 From: volker.simonis at gmail.com (Volker Simonis) Date: Fri, 24 May 2019 08:12:53 +0200 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: yes schrieb am Fr. 24. Mai 2019 um 02:45: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, > mainly in the HotSpot and build areas, starting back in 2012. Mikael is > also the project lead for the Portola project. How he has escaped becoming > a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. > Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] > https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > > From christoph.langer at sap.com Fri May 24 06:32:05 2019 From: christoph.langer at sap.com (Langer, Christoph) Date: Fri, 24 May 2019 06:32:05 +0000 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote:yes /Christoph > -----Original Message----- > From: jdk-dev On Behalf Of > jesper.wilhelmsson at oracle.com > Sent: Freitag, 24. Mai 2019 02:45 > To: jdk-dev at openjdk.java.net > Subject: CFV: New JDK Reviewer: Mikael Vidstedt > > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, > mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the > project lead for the Portola project. How he has escaped becoming a > Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes > must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] > https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael > )+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer From Alan.Bateman at oracle.com Fri May 24 06:31:51 2019 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Fri, 24 May 2019 07:31:51 +0100 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <2815b358-a99d-5ed8-2939-80d7c651aadb@oracle.com> On 24/05/2019 01:44, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Vote: yes From goetz.lindenmaier at sap.com Fri May 24 06:56:25 2019 From: goetz.lindenmaier at sap.com (Lindenmaier, Goetz) Date: Fri, 24 May 2019 06:56:25 +0000 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: vote: yes Best regards, Goetz. > -----Original Message----- > From: jdk-dev On Behalf Of > jesper.wilhelmsson at oracle.com > Sent: Freitag, 24. Mai 2019 02:45 > To: jdk-dev at openjdk.java.net > Subject: CFV: New JDK Reviewer: Mikael Vidstedt > > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly > in the HotSpot and build areas, starting back in 2012. Mikael is also the project > lead for the Portola project. How he has escaped becoming a Reviewer until > now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes > must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] > https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+o > r+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer From sean.coffey at oracle.com Fri May 24 07:54:20 2019 From: sean.coffey at oracle.com (=?UTF-8?Q?Se=c3=a1n_Coffey?=) Date: Fri, 24 May 2019 08:54:20 +0100 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <22abb653-9736-7148-0952-0825df1535da@oracle.com> Vote: Yes regards, Sean. On 24/05/2019 01:44, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From stefan.karlsson at oracle.com Fri May 24 07:58:50 2019 From: stefan.karlsson at oracle.com (Stefan Karlsson) Date: Fri, 24 May 2019 09:58:50 +0200 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <80dafe7e-43ac-1f84-afcf-46f9b9a80021@oracle.com> Vote: yes StefanK On 2019-05-24 02:44, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From tobias.hartmann at oracle.com Fri May 24 08:01:56 2019 From: tobias.hartmann at oracle.com (Tobias Hartmann) Date: Fri, 24 May 2019 10:01:56 +0200 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <71c69dfc-98ce-1664-19a8-a8f887f49eb0@oracle.com> Vote: yes Best regards, Tobias On 24.05.19 02:44, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From per.liden at oracle.com Fri May 24 08:04:26 2019 From: per.liden at oracle.com (Per Liden) Date: Fri, 24 May 2019 10:04:26 +0200 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <5416d6fe-de64-a227-a3e1-71503db8af0f@oracle.com> Vote: yes /Per On 5/24/19 2:44 AM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From martin.doerr at sap.com Fri May 24 08:17:29 2019 From: martin.doerr at sap.com (Doerr, Martin) Date: Fri, 24 May 2019 08:17:29 +0000 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <5416d6fe-de64-a227-a3e1-71503db8af0f@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> <5416d6fe-de64-a227-a3e1-71503db8af0f@oracle.com> Message-ID: Vote: yes Best regards, Martin From dmitry.markov at oracle.com Fri May 24 08:18:42 2019 From: dmitry.markov at oracle.com (Dmitry Markov) Date: Fri, 24 May 2019 09:18:42 +0100 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: yes Thanks, Dmitry > On 24 May 2019, at 01:44, jesper.wilhelmsson at oracle.com wrote: > > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From thomas.schatzl at oracle.com Fri May 24 08:47:02 2019 From: thomas.schatzl at oracle.com (Thomas Schatzl) Date: Fri, 24 May 2019 10:47:02 +0200 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: vote: yes Thomas From daniel.fuchs at oracle.com Fri May 24 08:53:00 2019 From: daniel.fuchs at oracle.com (Daniel Fuchs) Date: Fri, 24 May 2019 09:53:00 +0100 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: YES best regards, -- daniel On 24/05/2019 01:44, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. From serguei.spitsyn at oracle.com Fri May 24 10:03:20 2019 From: serguei.spitsyn at oracle.com (serguei.spitsyn at oracle.com) Date: Fri, 24 May 2019 03:03:20 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <2353f49d-2c12-71d9-9add-4e25af3b2277@oracle.com> Vote: yes From claes.redestad at oracle.com Fri May 24 10:08:06 2019 From: claes.redestad at oracle.com (Claes Redestad) Date: Fri, 24 May 2019 12:08:06 +0200 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <4643b1b3-df55-7322-6eae-cc1ec7ae723f@oracle.com> Vote: yes On 2019-05-24 02:44, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. From adinn at redhat.com Fri May 24 10:10:16 2019 From: adinn at redhat.com (Andrew Dinn) Date: Fri, 24 May 2019 11:10:16 +0100 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: yes On 24/05/2019 01:44, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > > -- regards, Andrew Dinn ----------- Senior Principal Software Engineer Red Hat UK Ltd Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander From Roger.Riggs at oracle.com Fri May 24 13:21:16 2019 From: Roger.Riggs at oracle.com (Roger Riggs) Date: Fri, 24 May 2019 09:21:16 -0400 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <2a99336e-7aca-77b1-2be5-a2c488c99d79@oracle.com> Vote: Yes On 05/23/2019 08:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. From harold.seigel at oracle.com Fri May 24 14:49:04 2019 From: harold.seigel at oracle.com (Harold Seigel) Date: Fri, 24 May 2019 10:49:04 -0400 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: yes Harold On 5/23/2019 8:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From vladimir.x.ivanov at oracle.com Fri May 24 15:31:15 2019 From: vladimir.x.ivanov at oracle.com (Vladimir Ivanov) Date: Fri, 24 May 2019 18:31:15 +0300 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <6a029ddd-1e2c-bf69-761e-47f0ed7284db@oracle.com> Vote: yes Best regards, Vladimir Ivanov On 24/05/2019 03:44, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. From calvin.cheung at oracle.com Fri May 24 15:39:42 2019 From: calvin.cheung at oracle.com (Calvin Cheung) Date: Fri, 24 May 2019 08:39:42 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <5CE8103E.2010407@oracle.com> Vote: yes On 5/23/19, 5:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From erik.joelsson at oracle.com Fri May 24 15:53:57 2019 From: erik.joelsson at oracle.com (Erik Joelsson) Date: Fri, 24 May 2019 08:53:57 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <3e1caad2-e099-6d00-0a69-94942ac275ea@oracle.com> Vote: yes /Erik On 2019-05-23 17:44, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From jesper.wilhelmsson at oracle.com Fri May 24 20:02:58 2019 From: jesper.wilhelmsson at oracle.com (jesper.wilhelmsson at oracle.com) Date: Fri, 24 May 2019 22:02:58 +0200 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <68AB76BA-CBC8-4D20-A5E0-CF68CC558B39@oracle.com> Vote: Yes /Jesper > On 24 May 2019, at 02:44, jesper.wilhelmsson at oracle.com wrote: > > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From kim.barrett at oracle.com Sat May 25 14:44:58 2019 From: kim.barrett at oracle.com (Kim Barrett) Date: Sat, 25 May 2019 10:44:58 -0400 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <36FCF5EA-32C5-48DE-A43B-8BC3560AAB9D@oracle.com> vote: yes > On May 23, 2019, at 8:44 PM, jesper.wilhelmsson at oracle.com wrote: > > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer From chris.hegarty at oracle.com Sat May 25 15:00:46 2019 From: chris.hegarty at oracle.com (Chris Hegarty) Date: Sat, 25 May 2019 16:00:46 +0100 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <78A68885-7815-4A3D-BFA6-BB0F9061A94A@oracle.com> Vote: YES -Chris. > On 24 May 2019, at 01:44, jesper.wilhelmsson at oracle.com wrote: > > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. From zgu at redhat.com Sat May 25 15:15:29 2019 From: zgu at redhat.com (Zhengyu Gu) Date: Sat, 25 May 2019 11:15:29 -0400 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <8e4217c1-9a34-f49e-185d-d4477038d95f@redhat.com> Vote: yes. -Zhengyu > > On 5/23/2019 8:44 PM, jesper.wilhelmsson at oracle.com wrote: >> I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. >> >> Mikael has contributed 127 changesets [1] to various parts of OpenJDK, >> mainly in the HotSpot and build areas, starting back in 2012. Mikael >> is also the project lead for the Portola project. How he has escaped >> becoming a Reviewer until now is a mystery. >> >> Votes are due by June 6, 2019. >> >> Only current JDK Reviewers [2] are eligible to vote on this >> nomination.? Votes must be cast in the open by replying to this >> mailing list. >> For Lazy Consensus voting instructions, see [3]. >> >> Thanks, >> /Jesper >> >> [1] >> https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() >> >> [2] http://openjdk.java.net/census >> [3] http://openjdk.java.net/projects/#project-reviewer >> From dean.long at oracle.com Sun May 26 07:09:08 2019 From: dean.long at oracle.com (dean.long at oracle.com) Date: Sun, 26 May 2019 00:09:08 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <5b44e14f-95f4-1fde-6a33-594a667217ac@oracle.com> Vote: yes On 5/23/19 5:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From weijun.wang at oracle.com Mon May 27 00:43:06 2019 From: weijun.wang at oracle.com (Weijun Wang) Date: Mon, 27 May 2019 08:43:06 +0800 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: yes --weijun > On May 24, 2019, at 8:44 AM, jesper.wilhelmsson at oracle.com wrote: > > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From coleen.phillimore at oracle.com Tue May 28 10:44:43 2019 From: coleen.phillimore at oracle.com (coleen.phillimore at oracle.com) Date: Tue, 28 May 2019 06:44:43 -0400 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <5e759446-1876-26d0-d430-3cac2acf9de0@oracle.com> Vote: yes On 5/23/19 8:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From robbin.ehn at oracle.com Tue May 28 10:44:46 2019 From: robbin.ehn at oracle.com (Robbin Ehn) Date: Tue, 28 May 2019 12:44:46 +0200 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <2119cba1-4424-2156-3a92-c2bd5b7fd2e3@oracle.com> Vote:yes /Robbin On 2019-05-24 02:44, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From peter.levart at gmail.com Tue May 28 11:25:47 2019 From: peter.levart at gmail.com (Peter Levart) Date: Tue, 28 May 2019 13:25:47 +0200 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: yes Regards, Peter On 5/24/19 2:44 AM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From lois.foltan at oracle.com Tue May 28 12:26:40 2019 From: lois.foltan at oracle.com (Lois Foltan) Date: Tue, 28 May 2019 08:26:40 -0400 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <2ec975be-fd5c-e455-85f3-051999372d37@oracle.com> vote: yes On 5/23/2019 8:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From christoph.langer at sap.com Tue May 28 12:34:35 2019 From: christoph.langer at sap.com (Langer, Christoph) Date: Tue, 28 May 2019 12:34:35 +0000 Subject: Result: New JDK Committer: Ralf Schmelter Message-ID: The voting for Ralf Schmelter (rschmelter) [1] is now closed. Yes: 14 Veto: 0 Abstain: 0 According to the Bylaws definition of Lazy Consensus, this is sufficient to approve the nomination. Thanks and regards, Christoph [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-May/002842.html From tprintezis at twitter.com Tue May 28 13:17:48 2019 From: tprintezis at twitter.com (Tony Printezis) Date: Tue, 28 May 2019 06:17:48 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: Vote: yes Tony ????? Tony Printezis | @TonyPrintezis | tprintezis at twitter.com On May 23, 2019 at 8:55:52 PM, jesper.wilhelmsson at oracle.com ( jesper.wilhelmsson at oracle.com) wrote: I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. Votes are due by June 6, 2019. Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. For Lazy Consensus voting instructions, see [3]. Thanks, /Jesper [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() [2] http://openjdk.java.net/census [3] http://openjdk.java.net/projects/#project-reviewer From erik.gahlin at oracle.com Tue May 28 13:21:35 2019 From: erik.gahlin at oracle.com (Erik Gahlin) Date: Tue, 28 May 2019 15:21:35 +0200 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <5CED35DF.2000305@oracle.com> Vote: yes Erik > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From mandy.chung at oracle.com Wed May 29 02:49:48 2019 From: mandy.chung at oracle.com (Mandy Chung) Date: Tue, 28 May 2019 19:49:48 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <6670e70a-a443-0f0d-be1c-f01c0f99aec5@oracle.com> Vote: yes Mandy On 5/23/2019 5:44 PM,jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, > mainly in the HotSpot and build areas, starting back in 2012. Mikael is > also the project lead for the Portola project. How he has escaped becoming > a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. > Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] > https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2]http://openjdk.java.net/census > [3]http://openjdk.java.net/projects/#project-reviewer From david.holmes at oracle.com Wed May 29 05:28:29 2019 From: david.holmes at oracle.com (David Holmes) Date: Wed, 29 May 2019 15:28:29 +1000 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <33761022-f6ef-2789-74d1-6b49829bb01e@oracle.com> Vote: yes David ----- On 24/05/2019 10:44 am, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From volker.simonis at gmail.com Wed May 29 12:46:14 2019 From: volker.simonis at gmail.com (Volker Simonis) Date: Wed, 29 May 2019 14:46:14 +0200 Subject: Result: New JDK Reviewer: Matthias Baesken Message-ID: Voting for Matthias Baesken [1] is now closed. Yes: 20 Veto: 0 Abstain: 0 According to the Bylaws definition of Three-Vote Consensus, this is sufficient to approve the nomination. Best regards, Volker [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-May/thread.html#2824 From mark.reinhold at oracle.com Wed May 29 16:22:04 2019 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Wed, 29 May 2019 09:22:04 -0700 Subject: JEP proposed to target JDK 13: 353: Reimplement the Legacy Socket API In-Reply-To: <20190516195614.B341C2AF56C@eggemoggin.niobe.net> References: <20190516195614.B341C2AF56C@eggemoggin.niobe.net> Message-ID: <20190529092204.221334692@eggemoggin.niobe.net> 2019/5/16 12:56:14 -0700, mark.reinhold at oracle.com: > The following JEP is proposed to target JDK 13: > > 353: Reimplement the Legacy Socket API > https://openjdk.java.net/jeps/353 > > Feedback on this proposal from JDK Project Committers and Reviewers [1] > is more than welcome, as are reasoned objections. If no such objections > are raised by 23:00 UTC on Thursday, 23 May, or if they?re raised and > then satisfactorily answered, then per the JEP 2.0 process proposal [2] > I?ll target this JEP to JDK 13. Hearing no objections, I?ve targeted this JEP to JDK 13. - Mark From mark.reinhold at oracle.com Wed May 29 21:22:57 2019 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Wed, 29 May 2019 14:22:57 -0700 (PDT) Subject: JEP proposed to target JDK 13: 355: Text Blocks (Preview) Message-ID: <20190529212257.F30092B0869@eggemoggin.niobe.net> The following JEP is proposed to target JDK 13: 355: Text Blocks (Preview) https://openjdk.java.net/jeps/355 Feedback on this proposal from JDK Project Committers and Reviewers [1] is more than welcome, as are reasoned objections. If no such objections are raised by 23:00 UTC on Wednesday, 5 June, or if they?re raised and then satisfactorily answered, then per the JEP 2.0 process proposal [2] I?ll target this JEP to JDK 13. - Mark [1] https://openjdk.java.net/census#jdk [2] https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html From Pavel_Simonovsky at bmc.com Wed May 15 13:42:13 2019 From: Pavel_Simonovsky at bmc.com (Simonovsky, Pavel) Date: Wed, 15 May 2019 13:42:13 +0000 Subject: Where is mail list of dev opnJdk11? Message-ID: <010ffa0d43844c2ba13c9a6685ece8b4@phx-exmbprd-02.adprod.bmc.com> I have a problem building opnJdk 11 at Linux. When I run : make test I get: Building target 'test' in configuration 'linux-x86_64-normal-server-release' Warning: No mercurial configuration present and no .src-rev Compiling 27 files for BUILD_FAILURE_HANDLER /data1/controlm/jdk11-1ddf9a99e4ad/test/failure_handler/src/share/classes/jdk/test/failurehandler/jtreg/GatherDiagnosticInfoObserver.java:123: error: no suitable method found for save(Map) rp.save(map); ^ method InterviewParameters.save(File) is not applicable (argument mismatch; Map cannot be converted to File) method InterviewParameters.save(Map) is not applicable (argument mismatch; Map cannot be converted to Map) where CAP#1,CAP#2 are fresh type-variables: CAP#1 extends Object from capture of ? CAP#2 extends Object from capture of ? Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some messages have been simplified; recompile with -Xdiags:verbose to get full output 1 error gmake[3]: *** [/data1/controlm/jdk11-1ddf9a99e4ad/build/linux-x86_64-normal-server-release/support/test/failure_handler/classes/_the.BUILD_FAILURE_HANDLER_batch] Error 1 gmake[2]: *** [build-test-failure-handler] Error 1 gmake[2]: *** Waiting for unfinished jobs.... ERROR: Build failed for target 'test' in configuration 'linux-x86_64-normal-server-release' (exit code 2) Stopping sjavac server === Output from failing command(s) repeated here === * For target support_test_failure_handler_classes__the.BUILD_FAILURE_HANDLER_batch: /data1/controlm/jdk11-1ddf9a99e4ad/test/failure_handler/src/share/classes/jdk/test/failurehandler/jtreg/GatherDiagnosticInfoObserver.java:123: error: no suitable method found for save(Map) rp.save(map); ^ method InterviewParameters.save(File) is not applicable (argument mismatch; Map cannot be converted to File) method InterviewParameters.save(Map) is not applicable (argument mismatch; Map cannot be converted to Map) where CAP#1,CAP#2 are fresh type-variables: CAP#1 extends Object from capture of ? CAP#2 extends Object from capture of ? Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. ... (rest of output omitted) * All command lines available in /data1/controlm/jdk11-1ddf9a99e4ad/build/linux-x86_64-normal-server-release/make-support/failure-logs. === End of repeated output === No indication of failed target found. Hint: Try searching the build log for '] Error'. Hint: See doc/building.html#troubleshooting for assistance. make[1]: *** [main] Error 1 make: *** [test] Error 2 Is there special mail list for JDK 11 - where I can ask about it? Simonovsky Pavel Multiplatform CONTROL-M BMC Israel Software Engineer Voice: + 972 3 7664648 Fax: + 972 3 6451100 Email: Pavel_Simonovsky at bmc.com From david.holmes at oracle.com Thu May 30 05:49:59 2019 From: david.holmes at oracle.com (David Holmes) Date: Thu, 30 May 2019 15:49:59 +1000 Subject: Where is mail list of dev opnJdk11? In-Reply-To: <010ffa0d43844c2ba13c9a6685ece8b4@phx-exmbprd-02.adprod.bmc.com> References: <010ffa0d43844c2ba13c9a6685ece8b4@phx-exmbprd-02.adprod.bmc.com> Message-ID: <2538aa14-1c89-0004-1da4-1dd2d7a34988@oracle.com> Hi Pavel, Build issues are normally best discussed on the build-dev mailing list. In this case I'd have to query what version of Java you are using for your Boot JDK? And what version of JDK 11 sources you are trying to build? Cheers, David On 15/05/2019 11:42 pm, Simonovsky, Pavel wrote: > I have a problem building opnJdk 11 at Linux. > When I run : > make test > > I get: > > Building target 'test' in configuration 'linux-x86_64-normal-server-release' > Warning: No mercurial configuration present and no .src-rev > Compiling 27 files for BUILD_FAILURE_HANDLER > /data1/controlm/jdk11-1ddf9a99e4ad/test/failure_handler/src/share/classes/jdk/test/failurehandler/jtreg/GatherDiagnosticInfoObserver.java:123: error: no suitable method found for save(Map) > rp.save(map); > ^ > method InterviewParameters.save(File) is not applicable > (argument mismatch; Map cannot be converted to File) > method InterviewParameters.save(Map) is not applicable > (argument mismatch; Map cannot be converted to Map) > where CAP#1,CAP#2 are fresh type-variables: > CAP#1 extends Object from capture of ? > CAP#2 extends Object from capture of ? > Note: Some input files use or override a deprecated API. > Note: Recompile with -Xlint:deprecation for details. > Note: Some messages have been simplified; recompile with -Xdiags:verbose to get full output > 1 error > gmake[3]: *** [/data1/controlm/jdk11-1ddf9a99e4ad/build/linux-x86_64-normal-server-release/support/test/failure_handler/classes/_the.BUILD_FAILURE_HANDLER_batch] Error 1 > gmake[2]: *** [build-test-failure-handler] Error 1 > gmake[2]: *** Waiting for unfinished jobs.... > > ERROR: Build failed for target 'test' in configuration 'linux-x86_64-normal-server-release' (exit code 2) > Stopping sjavac server > > === Output from failing command(s) repeated here === > * For target support_test_failure_handler_classes__the.BUILD_FAILURE_HANDLER_batch: > /data1/controlm/jdk11-1ddf9a99e4ad/test/failure_handler/src/share/classes/jdk/test/failurehandler/jtreg/GatherDiagnosticInfoObserver.java:123: error: no suitable method found for save(Map) > rp.save(map); > ^ > method InterviewParameters.save(File) is not applicable > (argument mismatch; Map cannot be converted to File) > method InterviewParameters.save(Map) is not applicable > (argument mismatch; Map cannot be converted to Map) > where CAP#1,CAP#2 are fresh type-variables: > CAP#1 extends Object from capture of ? > CAP#2 extends Object from capture of ? > Note: Some input files use or override a deprecated API. > Note: Recompile with -Xlint:deprecation for details. > ... (rest of output omitted) > > * All command lines available in /data1/controlm/jdk11-1ddf9a99e4ad/build/linux-x86_64-normal-server-release/make-support/failure-logs. > === End of repeated output === > > No indication of failed target found. > Hint: Try searching the build log for '] Error'. > Hint: See doc/building.html#troubleshooting for assistance. > > make[1]: *** [main] Error 1 > make: *** [test] Error 2 > > Is there special mail list for JDK 11 - where I can ask about it? > > Simonovsky Pavel > Multiplatform CONTROL-M BMC Israel > Software Engineer > Voice: + 972 3 7664648 > Fax: + 972 3 6451100 > Email: Pavel_Simonovsky at bmc.com > From mark.reinhold at oracle.com Thu May 30 21:09:11 2019 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Thu, 30 May 2019 14:09:11 -0700 (PDT) Subject: JEP proposed to target JDK 13: 354: Switch Expressions (Preview) Message-ID: <20190530210911.73F0E2B0915@eggemoggin.niobe.net> The following JEP is proposed to target JDK 13: 354: Switch Expressions (Preview) https://openjdk.java.net/jeps/354 Feedback on this proposal from JDK Project Committers and Reviewers [1] is more than welcome, as are reasoned objections. If no such objections are raised by 23:00 UTC on Thursday, 6 June, or if they?re raised and then satisfactorily answered, then per the JEP 2.0 process proposal [2] I?ll target this JEP to JDK 13. - Mark [1] https://openjdk.java.net/census#jdk [2] https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html From martin.doerr at sap.com Fri May 31 11:03:19 2019 From: martin.doerr at sap.com (Doerr, Martin) Date: Fri, 31 May 2019 11:03:19 +0000 Subject: Result: New JDK Committer: Richard Reingruber Message-ID: The voting for Richard Reingruber (rrich) [1] is now closed. Yes: 15 Veto: 0 Abstain: 0 According to the Bylaws definition of Lazy Consensus, this is sufficient to approve the nomination. Thanks and best regards, Martin [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-May/002909.html From christoph.langer at sap.com Fri May 31 15:13:28 2019 From: christoph.langer at sap.com (Langer, Christoph) Date: Fri, 31 May 2019 15:13:28 +0000 Subject: Result: New JDK Committer: Ichiroh Takiguchi Message-ID: The voting for Ichiroh Takiguchi (itakiguchi) [1] is now closed. Yes: 9 Veto: 0 Abstain: 0 According to the Bylaws definition of Lazy Consensus, this is sufficient to approve the nomination. Thanks and Best Regards, Christoph [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-May/002898.html From bradford.wetmore at oracle.com Fri May 31 20:06:37 2019 From: bradford.wetmore at oracle.com (Bradford Wetmore) Date: Fri, 31 May 2019 13:06:37 -0700 Subject: CFV: New JDK Reviewer: Mikael Vidstedt In-Reply-To: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> References: <68C0365A-99F9-43AE-806B-ACADDE097591@oracle.com> Message-ID: <98b2a2d2-efdf-0970-6ccd-d7b1af7bf4d3@oracle.com> Vote: yes Brad On 5/23/2019 5:44 PM, jesper.wilhelmsson at oracle.com wrote: > I hereby nominate Mikael Vidstedt (mikael) to JDK Reviewer. > > Mikael has contributed 127 changesets [1] to various parts of OpenJDK, mainly in the HotSpot and build areas, starting back in 2012. Mikael is also the project lead for the Portola project. How he has escaped becoming a Reviewer until now is a mystery. > > Votes are due by June 6, 2019. > > Only current JDK Reviewers [2] are eligible to vote on this nomination. Votes must be cast in the open by replying to this mailing list. > For Lazy Consensus voting instructions, see [3]. > > Thanks, > /Jesper > > [1] https://hg.openjdk.java.net/jdk/jdk/log?revcount=200&rev=(author(mikael)+or+desc(%22mikael.vidstedt at oracle.com%22))+and+not+merge() > [2] http://openjdk.java.net/census > [3] http://openjdk.java.net/projects/#project-reviewer > From jonathan.gibbons at oracle.com Fri May 31 21:02:57 2019 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Fri, 31 May 2019 14:02:57 -0700 Subject: RFR: docs JDK-8225134: Update man-page files Message-ID: <40d2e8ce-9302-a6e1-a2a1-c98c251c7661@oracle.com> Please review a change to refresh the content of the man pages (*.1 files) in the main repo, to contain essentially the exact same content as found in the Oracle JDK man pages. Going forward, the intent is to bulk-update these pages towards the end of each release cycle, until we can eventually open source the underlying files from which the man pages are derived, at which time these files will be deleted. This email is to build-dev at ojn, even though there are no Makefile changes, because that list includes the folk mostly likely to make direct use of these files.? It is also cc jdk-dev at ojn so that the OpenJDK community is generally aware of this change. Note, although the current man pages share a history with the previous versions of these files, the transformations that have occurred between then and now make it all but impossible to compare the versions side by side with diff. For those folk wanting to review the content, it is best to look at the "New" or "Raw" files in the webrev. -- Jon JBS: https://bugs.openjdk.java.net/browse/JDK-8225134 Webrev: http://cr.openjdk.java.net/~jjg/8225134/webrev.00/webrev/ From erik.joelsson at oracle.com Fri May 31 21:31:29 2019 From: erik.joelsson at oracle.com (Erik Joelsson) Date: Fri, 31 May 2019 14:31:29 -0700 Subject: RFR: docs JDK-8225134: Update man-page files In-Reply-To: <40d2e8ce-9302-a6e1-a2a1-c98c251c7661@oracle.com> References: <40d2e8ce-9302-a6e1-a2a1-c98c251c7661@oracle.com> Message-ID: <075cb653-155a-4398-f5e9-2bb2b7ca1f7d@oracle.com> Looks good to me. /Erik On 2019-05-31 14:02, Jonathan Gibbons wrote: > Please review a change to refresh the content of the man pages (*.1 > files) in the main repo, > to contain essentially the exact same content as found in the Oracle > JDK man pages. > > Going forward, the intent is to bulk-update these pages towards the > end of each release > cycle, until we can eventually open source the underlying files from > which the man pages > are derived, at which time these files will be deleted. > > This email is to build-dev at ojn, even though there are no Makefile > changes, because that > list includes the folk mostly likely to make direct use of these > files.? It is also cc jdk-dev at ojn > so that the OpenJDK community is generally aware of this change. > > Note, although the current man pages share a history with the previous > versions of these > files, the transformations that have occurred between then and now > make it all but > impossible to compare the versions side by side with diff. For those > folk wanting to review > the content, it is best to look at the "New" or "Raw" files in the > webrev. > > -- Jon > > JBS: https://bugs.openjdk.java.net/browse/JDK-8225134 > Webrev: http://cr.openjdk.java.net/~jjg/8225134/webrev.00/webrev/ > > From mandy.chung at oracle.com Fri May 31 23:25:30 2019 From: mandy.chung at oracle.com (Mandy Chung) Date: Fri, 31 May 2019 16:25:30 -0700 Subject: RFR: docs JDK-8225134: Update man-page files In-Reply-To: <40d2e8ce-9302-a6e1-a2a1-c98c251c7661@oracle.com> References: <40d2e8ce-9302-a6e1-a2a1-c98c251c7661@oracle.com> Message-ID: <2818197a-ee23-9673-32e2-7e3951a20135@oracle.com> Bringing these pages to more recent version is better than the current so outdated version even it's just a snapshot. The list of new pages look okay (but I didn't validate the content.) Mandy On 5/31/19 2:02 PM, Jonathan Gibbons wrote: > Please review a change to refresh the content of the man pages (*.1 > files) in the main repo, > to contain essentially the exact same content as found in the Oracle > JDK man pages. > > Going forward, the intent is to bulk-update these pages towards the > end of each release > cycle, until we can eventually open source the underlying files from > which the man pages > are derived, at which time these files will be deleted. > > This email is to build-dev at ojn, even though there are no Makefile > changes, because that > list includes the folk mostly likely to make direct use of these > files.? It is also cc jdk-dev at ojn > so that the OpenJDK community is generally aware of this change. > > Note, although the current man pages share a history with the previous > versions of these > files, the transformations that have occurred between then and now > make it all but > impossible to compare the versions side by side with diff. For those > folk wanting to review > the content, it is best to look at the "New" or "Raw" files in the > webrev. > > -- Jon > > JBS: https://bugs.openjdk.java.net/browse/JDK-8225134 > Webrev: http://cr.openjdk.java.net/~jjg/8225134/webrev.00/webrev/ > >