From magnus.ihse.bursie at oracle.com Sun Apr 1 07:35:25 2018 From: magnus.ihse.bursie at oracle.com (Magnus Ihse Bursie) Date: Sun, 1 Apr 2018 09:35:25 +0200 Subject: New Project Proposal: The Block GC Message-ID: <22127101-8854-cd1b-7be4-43b7d162aa96@oracle.com> I hereby propose the creation of the Block GC Project with myself (Magnus Ihse Bursie) as the Lead and the Build Group as the sponsoring group. In accordance with the OpenJDK guidelines [1], this project will provide the Block GC, a creative new approach of handling GC mis-optimization.[2] The Block GC, also known as the Block Chain GC, is an innovative new system for Garbage Collection. It is a well-known fact that even though the JVM can be fine-tuned to employ an optimal GC method for a specific payload, most users do not bother to do so, or lack the technical skills needed to select the proper GC. The Block GC is a "parasitic" GC, in that it does not provide a separate GC system of it own, but instead selects the most optimal GC for each individual payload. As a unique feature, the Block GC will measure and accurately calculate the improvement provided by selecting the optimal GC method, compared to the GC previously selected. Let T_gc_def be the time the user application is stopped during the GC for the default GC settings, and let T_gc_opt be the corresponding time using the optimal GC method selected by the Block GC. The difference T_gc_def - T_gc_opt is the improvement in pausetime provided by the Block GC, and is known as the "block gain". The block gain can be seen as a hidden resource, available for free from the user of the JRE. After the GC has finished, the JRE can use the time provided by the block gain, with the user threads still suspended, without the application suffering performance regressions. In the initial implementation of the Block GC, the block gain was just used to let the JVM sleep for an amount of time corresponding to the block gain. This gave us a simple way to save processor cycles, and hence energy, thus providing a simple way for the Java user to help fight climate change without even noticing it. While a noble goal, this does not really makes business sense. In the updated version of the Block GC, which we propose to be added as the default GC in JDK 11, the block gain is instead used to calculate hash values for popular cryptocurrencies, a.k.a. "bitcoin mining". Our estimates show that this can generate a significant amount of revenue; with a projected ~50 M downloads of JDK 11, running typical workloads, and with typical values for GC settings (default or misconfigured), $50k/day for all OpenJDK installations worldwide is not unreasonable. This is a pure win-win scenario. The user will not notice any performance regression compared to the previous GC settings, and the cryptocurrency account proprietor will benefit fiscally. The user can set their own blockchain account, instead of the default, by issuing this command: java -XX:UnlockDangerousOptions -XX:UnsupportedGCOption=new_provider_config: where points to a configuration file in ASN.1 format describing the blockchain account. We hope to finish the documentation of this file in time for the release, but if not done, it will not be considered a release blocker. If a user override is not provided as above, by default, the revenue extracted by the Block GC miner will be stored in the Block GC Project account. This revenue will be divided as follows: 90% will go to the initial committers of the Block GC Project, and 10% will go to the OpenJDK community. The first installment of the 10% payment to the OpenJDK comminuty will be issued exactly one year from now, on April 1st 2019.[3] A preview of the Block GC can be found here: http://openjdk.java.net/preview/thisisunbelievable. The initial Committers will be: Magnus Ihse Bursie, Satoshi Nakamoto and P. T. Barnum. /Magnus [1] http://openjdk.java.net/projects/#new-project [2] http://openjdk.java.net/preview/thisisunbelievable [3] https://en.wikipedia.org/wiki/April_Fools%27_Day From forax at univ-mlv.fr Sun Apr 1 09:07:04 2018 From: forax at univ-mlv.fr (Remi Forax) Date: Sun, 1 Apr 2018 11:07:04 +0200 (CEST) Subject: New Project Proposal: The Block GC In-Reply-To: <22127101-8854-cd1b-7be4-43b7d162aa96@oracle.com> References: <22127101-8854-cd1b-7be4-43b7d162aa96@oracle.com> Message-ID: <1326562041.2464535.1522573624213.JavaMail.zimbra@u-pem.fr> As a coin-artist, i think it's important to support this kind of innovative revolution, so to improve the velocity of the introduction of the blockchain technology inside the Java ecosystem, i propose to start an ICO (Initial Con-Offering) using Duke Coin as token support. The white paper describing the exact offering is available at [1]. R?mi PS: Early investors can already wire the cash to my personal bitcoin account, to be sure to be part of this fantastic, one in a lifetime, opportunity. [1] http://openjdk.java.net/preview/thisisunbelievable/whitepaper ----- Mail original ----- > De: "Magnus Ihse Bursie" > ?: "discuss" > Envoy?: Dimanche 1 Avril 2018 09:35:25 > Objet: New Project Proposal: The Block GC > I hereby propose the creation of the Block GC Project with myself > (Magnus Ihse Bursie) as the Lead and the Build Group as the sponsoring > group. > > In accordance with the OpenJDK guidelines [1], this project will provide > the Block GC, a creative new approach of handling GC mis-optimization.[2] > > The Block GC, also known as the Block Chain GC, is an innovative new > system for Garbage Collection. It is a well-known fact that even though > the JVM can be fine-tuned to employ an optimal GC method for a specific > payload, most users do not bother to do so, or lack the technical skills > needed to select the proper GC. The Block GC is a "parasitic" GC, in > that it does not provide a separate GC system of it own, but instead > selects the most optimal GC for each individual payload. > > As a unique feature, the Block GC will measure and accurately calculate > the improvement provided by selecting the optimal GC method, compared to > the GC previously selected. Let T_gc_def be the time the user > application is stopped during the GC for the default GC settings, and > let T_gc_opt be the corresponding time using the optimal GC method > selected by the Block GC. The difference T_gc_def - T_gc_opt is the > improvement in pausetime provided by the Block GC, and is known as the > "block gain". > > The block gain can be seen as a hidden resource, available for free from > the user of the JRE. After the GC has finished, the JRE can use the time > provided by the block gain, with the user threads still suspended, > without the application suffering performance regressions. In the > initial implementation of the Block GC, the block gain was just used to > let the JVM sleep for an amount of time corresponding to the block gain. > This gave us a simple way to save processor cycles, and hence energy, > thus providing a simple way for the Java user to help fight climate > change without even noticing it. > > While a noble goal, this does not really makes business sense. In the > updated version of the Block GC, which we propose to be added as the > default GC in JDK 11, the block gain is instead used to calculate hash > values for popular cryptocurrencies, a.k.a. "bitcoin mining". Our > estimates show that this can generate a significant amount of revenue; > with a projected ~50 M downloads of JDK 11, running typical workloads, > and with typical values for GC settings (default or misconfigured), > $50k/day for all OpenJDK installations worldwide is not unreasonable. > > This is a pure win-win scenario. The user will not notice any > performance regression compared to the previous GC settings, and the > cryptocurrency account proprietor will benefit fiscally. > > The user can set their own blockchain account, instead of the default, > by issuing this command: > > java -XX:UnlockDangerousOptions > -XX:UnsupportedGCOption=new_provider_config: > > where points to a configuration file in ASN.1 > format describing the blockchain account. We hope to finish the > documentation of this file in time for the release, but if not done, it > will not be considered a release blocker. > > If a user override is not provided as above, by default, the revenue > extracted by the Block GC miner will be stored in the Block GC Project > account. This revenue will be divided as follows: 90% will go to the > initial committers of the Block GC Project, and 10% will go to the > OpenJDK community. > > The first installment of the 10% payment to the OpenJDK comminuty will > be issued exactly one year from now, on April 1st 2019.[3] > > A preview of the Block GC can be found here: > http://openjdk.java.net/preview/thisisunbelievable. > > The initial Committers will be: Magnus Ihse Bursie, Satoshi Nakamoto and > P. T. Barnum. > > /Magnus > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/preview/thisisunbelievable > [3] https://en.wikipedia.org/wiki/April_Fools%27_Day From roman at kennke.org Sun Apr 1 10:03:17 2018 From: roman at kennke.org (Roman Kennke) Date: Sun, 01 Apr 2018 12:03:17 +0200 Subject: New Project Proposal: The Block GC In-Reply-To: <22127101-8854-cd1b-7be4-43b7d162aa96@oracle.com> References: <22127101-8854-cd1b-7be4-43b7d162aa96@oracle.com> Message-ID: <4522A1D2-D567-46E9-A69B-0250B7F6DB7A@kennke.org> I like the proposal. The block chain technology can be leveraged to further help with memory management. We could simply store any Java heap transaction in the block chain, indefinitely. I propose to handle any latency, throughput or capacity concerns by throwing more buzzwords on it. We can do that because the block chain provides a perfect abstraction layer from reality. Cheers, Roman Am 1. April 2018 09:35:25 MESZ schrieb Magnus Ihse Bursie : >I hereby propose the creation of the Block GC Project with myself >(Magnus Ihse Bursie) as the Lead and the Build Group as the sponsoring >group. > >In accordance with the OpenJDK guidelines [1], this project will >provide >the Block GC, a creative new approach of handling GC >mis-optimization.[2] > >The Block GC, also known as the Block Chain GC, is an innovative new >system for Garbage Collection. It is a well-known fact that even though > >the JVM can be fine-tuned to employ an optimal GC method for a specific > >payload, most users do not bother to do so, or lack the technical >skills >needed to select the proper GC. The Block GC is a "parasitic" GC, in >that it does not provide a separate GC system of it own, but instead >selects the most optimal GC for each individual payload. > >As a unique feature, the Block GC will measure and accurately calculate > >the improvement provided by selecting the optimal GC method, compared >to >the GC previously selected. Let T_gc_def be the time the user >application is stopped during the GC for the default GC settings, and >let T_gc_opt be the corresponding time using the optimal GC method >selected by the Block GC. The difference T_gc_def - T_gc_opt is the >improvement in pausetime provided by the Block GC, and is known as the >"block gain". > >The block gain can be seen as a hidden resource, available for free >from >the user of the JRE. After the GC has finished, the JRE can use the >time >provided by the block gain, with the user threads still suspended, >without the application suffering performance regressions. In the >initial implementation of the Block GC, the block gain was just used to > >let the JVM sleep for an amount of time corresponding to the block >gain. >This gave us a simple way to save processor cycles, and hence energy, >thus providing a simple way for the Java user to help fight climate >change without even noticing it. > >While a noble goal, this does not really makes business sense. In the >updated version of the Block GC, which we propose to be added as the >default GC in JDK 11, the block gain is instead used to calculate hash >values for popular cryptocurrencies, a.k.a. "bitcoin mining". Our >estimates show that this can generate a significant amount of revenue; >with a projected ~50 M downloads of JDK 11, running typical workloads, >and with typical values for GC settings (default or misconfigured), >$50k/day for all OpenJDK installations worldwide is not unreasonable. > >This is a pure win-win scenario. The user will not notice any >performance regression compared to the previous GC settings, and the >cryptocurrency account proprietor will benefit fiscally. > >The user can set their own blockchain account, instead of the default, >by issuing this command: > > java -XX:UnlockDangerousOptions >-XX:UnsupportedGCOption=new_provider_config: > >where points to a configuration file in ASN.1 >format describing the blockchain account. We hope to finish the >documentation of this file in time for the release, but if not done, it > >will not be considered a release blocker. > >If a user override is not provided as above, by default, the revenue >extracted by the Block GC miner will be stored in the Block GC Project >account. This revenue will be divided as follows: 90% will go to the >initial committers of the Block GC Project, and 10% will go to the >OpenJDK community. > >The first installment of the 10% payment to the OpenJDK comminuty will >be issued exactly one year from now, on April 1st 2019.[3] > >A preview of the Block GC can be found here: >http://openjdk.java.net/preview/thisisunbelievable. > >The initial Committers will be: Magnus Ihse Bursie, Satoshi Nakamoto >and >P. T. Barnum. > >/Magnus > >[1] http://openjdk.java.net/projects/#new-project >[2] http://openjdk.java.net/preview/thisisunbelievable >[3] https://en.wikipedia.org/wiki/April_Fools%27_Day -- Diese Nachricht wurde von meinem Android-Ger?t mit K-9 Mail gesendet. From roman at kennke.org Sun Apr 1 10:47:25 2018 From: roman at kennke.org (Roman Kennke) Date: Sun, 01 Apr 2018 12:47:25 +0200 Subject: New Project Proposal: The Block GC In-Reply-To: <4522A1D2-D567-46E9-A69B-0250B7F6DB7A@kennke.org> References: <22127101-8854-cd1b-7be4-43b7d162aa96@oracle.com> <4522A1D2-D567-46E9-A69B-0250B7F6DB7A@kennke.org> Message-ID: <07AD2545-59DB-43EC-BBE3-6ADDC0749D05@kennke.org> Duh. I skipped that the point of this scheme is that it obviates the need to do any GC, and thus avoids any complex algorithms. Am 1. April 2018 12:03:17 MESZ schrieb Roman Kennke : >I like the proposal. >The block chain technology can be leveraged to further help with memory >management. We could simply store any Java heap transaction in the >block chain, indefinitely. I propose to handle any latency, throughput >or capacity concerns by throwing more buzzwords on it. We can do that >because the block chain provides a perfect abstraction layer from >reality. > >Cheers, Roman > >Am 1. April 2018 09:35:25 MESZ schrieb Magnus Ihse Bursie >: >>I hereby propose the creation of the Block GC Project with myself >>(Magnus Ihse Bursie) as the Lead and the Build Group as the sponsoring > >>group. >> >>In accordance with the OpenJDK guidelines [1], this project will >>provide >>the Block GC, a creative new approach of handling GC >>mis-optimization.[2] >> >>The Block GC, also known as the Block Chain GC, is an innovative new >>system for Garbage Collection. It is a well-known fact that even >though >> >>the JVM can be fine-tuned to employ an optimal GC method for a >specific >> >>payload, most users do not bother to do so, or lack the technical >>skills >>needed to select the proper GC. The Block GC is a "parasitic" GC, in >>that it does not provide a separate GC system of it own, but instead >>selects the most optimal GC for each individual payload. >> >>As a unique feature, the Block GC will measure and accurately >calculate >> >>the improvement provided by selecting the optimal GC method, compared >>to >>the GC previously selected. Let T_gc_def be the time the user >>application is stopped during the GC for the default GC settings, and >>let T_gc_opt be the corresponding time using the optimal GC method >>selected by the Block GC. The difference T_gc_def - T_gc_opt is the >>improvement in pausetime provided by the Block GC, and is known as the > >>"block gain". >> >>The block gain can be seen as a hidden resource, available for free >>from >>the user of the JRE. After the GC has finished, the JRE can use the >>time >>provided by the block gain, with the user threads still suspended, >>without the application suffering performance regressions. In the >>initial implementation of the Block GC, the block gain was just used >to >> >>let the JVM sleep for an amount of time corresponding to the block >>gain. >>This gave us a simple way to save processor cycles, and hence energy, >>thus providing a simple way for the Java user to help fight climate >>change without even noticing it. >> >>While a noble goal, this does not really makes business sense. In the >>updated version of the Block GC, which we propose to be added as the >>default GC in JDK 11, the block gain is instead used to calculate hash > >>values for popular cryptocurrencies, a.k.a. "bitcoin mining". Our >>estimates show that this can generate a significant amount of revenue; > >>with a projected ~50 M downloads of JDK 11, running typical workloads, > >>and with typical values for GC settings (default or misconfigured), >>$50k/day for all OpenJDK installations worldwide is not unreasonable. >> >>This is a pure win-win scenario. The user will not notice any >>performance regression compared to the previous GC settings, and the >>cryptocurrency account proprietor will benefit fiscally. >> >>The user can set their own blockchain account, instead of the default, > >>by issuing this command: >> >> java -XX:UnlockDangerousOptions >>-XX:UnsupportedGCOption=new_provider_config: >> >>where points to a configuration file in ASN.1 >>format describing the blockchain account. We hope to finish the >>documentation of this file in time for the release, but if not done, >it >> >>will not be considered a release blocker. >> >>If a user override is not provided as above, by default, the revenue >>extracted by the Block GC miner will be stored in the Block GC Project > >>account. This revenue will be divided as follows: 90% will go to the >>initial committers of the Block GC Project, and 10% will go to the >>OpenJDK community. >> >>The first installment of the 10% payment to the OpenJDK comminuty will > >>be issued exactly one year from now, on April 1st 2019.[3] >> >>A preview of the Block GC can be found here: >>http://openjdk.java.net/preview/thisisunbelievable. >> >>The initial Committers will be: Magnus Ihse Bursie, Satoshi Nakamoto >>and >>P. T. Barnum. >> >>/Magnus >> >>[1] http://openjdk.java.net/projects/#new-project >>[2] http://openjdk.java.net/preview/thisisunbelievable >>[3] https://en.wikipedia.org/wiki/April_Fools%27_Day -- Diese Nachricht wurde von meinem Android-Ger?t mit K-9 Mail gesendet. From neugens.limasoftware at gmail.com Sun Apr 1 12:04:51 2018 From: neugens.limasoftware at gmail.com (Mario Torre) Date: Sun, 01 Apr 2018 12:04:51 +0000 Subject: New project proposal: even faster JDK releases Message-ID: I hereby propose the creation of project Doomed, which aims to solve an extremely important issue caused by the currently specified fast release schedule, that of an equally fast adoption. With project Doomed we aim at continuous release and deployment of the JDK, thus removing the need to have any version number and increase the adoption rate considerably[1] and better position the JDK in the fast pacing world of cloud development. In order to better help the new release cycle, which of course is not a cycle but a continuous stream of random bits, we also propose the complete abolition of testing and reviews, instead developers should just commit whatever they feel like whenever they feel so, possibly on Friday night. Support for random and unnecessary updates delivery will be added today in the repositories with a simple GO application that will show an annoying pop up on user desktop, or, in case of headless deployments, will both send an email to the administrator (the user you generally contact when you have a trouble with your Windows installation) or, if using Linux a web server telling everyone of your users how to recompile the kernel yourself to keep the JDK updated. OSX developers will not be warned because they use it wrong anyway. Being a GO application this will be fast and consume no resources at all, so no users will ever complain, which would have happened if we used a JavaFX application instead. Please note, the goal of project Doomed is not to replace the Java programming language with GO, since support for this proposal will come in a separate email next year. With continuous releases we hope that users will finally be happy and not complain anymore that Java evolves too slowly while still using JDK 6 in all their deployments, especially users that are part of the Java Champions initiative, instead we are offering the state of the art and at the same time guarantee that no application will ever run for more than a minute or two, no matter what version of the JDK, the ultimate extreme compatibility effort. Votes are due today 1st of April, at 23:61, although a decision has already been made so the votes don?t really matter. Cheers, Mario [1] In fact, we may even drop the adoption rate completely, which is still a way to solve the problem! From org.openjdk at io7m.com Sun Apr 1 12:32:05 2018 From: org.openjdk at io7m.com (Mark Raynsford) Date: Sun, 1 Apr 2018 12:32:05 +0000 Subject: New project proposal: even faster JDK releases In-Reply-To: References: Message-ID: <20180401123205.0a18ad0c@copperhead.int.arc7.info> On 2018-04-01T12:04:51 +0000 Mario Torre wrote: > > In order to better help the new release cycle, which of course is not a > cycle but a continuous stream of random bits, we also propose the complete > abolition of testing and reviews, instead developers should just commit > whatever they feel like whenever they feel so, possibly on Friday night. In addition to this, I'm currently working on a system that will allow developers to get code into releases *before* they've actually committed it. This, does, however, currently depend on the availability of sun.misc.Unsafe [1] and will therefore require the introduction of new APIs via JEP proposals for future inclusion. To coincide with the new even-faster-release cycle, I suggest that we adopt a new JEP release cycle: The last person to stop speaking about a new JEP feature on any given mailing list is declared the winner and their implementation is immediately committed as-is [2]. [1] See the following whitepaper for details: http://insecure.org/stf/smashstack.html [2] An alternate process was considered involving competitive shin-kicking [3]. Unfortunately, during testing, the last person standing was rendered unable to accurately describe the enhancement in question (or indeed, to speak anything resembling human language at all) and the idea was dropped in favour of arguments on mailing lists. [3] https://en.wikipedia.org/wiki/Shin-kicking -- Mark Raynsford | http://www.io7m.com From mrinal.kanti at gmail.com Sun Apr 1 18:04:08 2018 From: mrinal.kanti at gmail.com (Mrinal Kanti) Date: Sun, 1 Apr 2018 23:34:08 +0530 Subject: New Project Proposal: The Block GC In-Reply-To: <22127101-8854-cd1b-7be4-43b7d162aa96@oracle.com> References: <22127101-8854-cd1b-7be4-43b7d162aa96@oracle.com> Message-ID: May I suggest to throw in some crypto-mining code which could run while the sysadmins and monitoring agents are under the impression that its the GC behavior that's being optimized under the hood. Farms of enterprise server clusters couldn't have been better utilized. Definitely sounds more efficient than the browser plugin approach. On Sun, Apr 1, 2018 at 1:05 PM, Magnus Ihse Bursie < magnus.ihse.bursie at oracle.com> wrote: > I hereby propose the creation of the Block GC Project with myself (Magnus > Ihse Bursie) as the Lead and the Build Group as the sponsoring group. > > In accordance with the OpenJDK guidelines [1], this project will provide > the Block GC, a creative new approach of handling GC mis-optimization.[2] > > The Block GC, also known as the Block Chain GC, is an innovative new > system for Garbage Collection. It is a well-known fact that even though the > JVM can be fine-tuned to employ an optimal GC method for a specific > payload, most users do not bother to do so, or lack the technical skills > needed to select the proper GC. The Block GC is a "parasitic" GC, in that > it does not provide a separate GC system of it own, but instead selects the > most optimal GC for each individual payload. > > As a unique feature, the Block GC will measure and accurately calculate > the improvement provided by selecting the optimal GC method, compared to > the GC previously selected. Let T_gc_def be the time the user application > is stopped during the GC for the default GC settings, and let T_gc_opt be > the corresponding time using the optimal GC method selected by the Block > GC. The difference T_gc_def - T_gc_opt is the improvement in pausetime > provided by the Block GC, and is known as the "block gain". > > The block gain can be seen as a hidden resource, available for free from > the user of the JRE. After the GC has finished, the JRE can use the time > provided by the block gain, with the user threads still suspended, without > the application suffering performance regressions. In the initial > implementation of the Block GC, the block gain was just used to let the JVM > sleep for an amount of time corresponding to the block gain. This gave us a > simple way to save processor cycles, and hence energy, thus providing a > simple way for the Java user to help fight climate change without even > noticing it. > > While a noble goal, this does not really makes business sense. In the > updated version of the Block GC, which we propose to be added as the > default GC in JDK 11, the block gain is instead used to calculate hash > values for popular cryptocurrencies, a.k.a. "bitcoin mining". Our estimates > show that this can generate a significant amount of revenue; with a > projected ~50 M downloads of JDK 11, running typical workloads, and with > typical values for GC settings (default or misconfigured), $50k/day for all > OpenJDK installations worldwide is not unreasonable. > > This is a pure win-win scenario. The user will not notice any performance > regression compared to the previous GC settings, and the cryptocurrency > account proprietor will benefit fiscally. > > The user can set their own blockchain account, instead of the default, by > issuing this command: > > java -XX:UnlockDangerousOptions -XX:UnsupportedGCOption=new_provider_config: to config file> > > where points to a configuration file in ASN.1 format > describing the blockchain account. We hope to finish the documentation of > this file in time for the release, but if not done, it will not be > considered a release blocker. > > If a user override is not provided as above, by default, the revenue > extracted by the Block GC miner will be stored in the Block GC Project > account. This revenue will be divided as follows: 90% will go to the > initial committers of the Block GC Project, and 10% will go to the OpenJDK > community. > > The first installment of the 10% payment to the OpenJDK comminuty will be > issued exactly one year from now, on April 1st 2019.[3] > > A preview of the Block GC can be found here: > http://openjdk.java.net/preview/thisisunbelievable. > > The initial Committers will be: Magnus Ihse Bursie, Satoshi Nakamoto and > P. T. Barnum. > > /Magnus > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/preview/thisisunbelievable > [3] https://en.wikipedia.org/wiki/April_Fools%27_Day > > From benjamin.john.evans at gmail.com Mon Apr 2 00:27:03 2018 From: benjamin.john.evans at gmail.com (Ben Evans) Date: Mon, 02 Apr 2018 00:27:03 +0000 Subject: New Project Proposal: The Block GC In-Reply-To: <22127101-8854-cd1b-7be4-43b7d162aa96@oracle.com> References: <22127101-8854-cd1b-7be4-43b7d162aa96@oracle.com> Message-ID: Given Oracle?s ongoing chronic under-investment in the Java platform, I propose that we should fund this via non-traditional means. We should hold an ICO - selling 1bn Garbage tokens (symbol GBO) to raise funds for the necessary engineering work. This will totally not be a security, as the GBO token will convey the right to not run GC at all, and have it done elsewhere in the network. This is completely technically feasible & not something we made up. Also because we say that it isn?t a security, the SEC is totally fine with that. I propose a starting value of 1 GBO == 1 tulip bulb, or 2.7 Updog. I can probably have GBO listed on major crypto currency exchanges by Monday morning... Ben On Sun, 1 Apr 2018 at 03:35, Magnus Ihse Bursie < magnus.ihse.bursie at oracle.com> wrote: > I hereby propose the creation of the Block GC Project with myself > (Magnus Ihse Bursie) as the Lead and the Build Group as the sponsoring > group. > > In accordance with the OpenJDK guidelines [1], this project will provide > the Block GC, a creative new approach of handling GC mis-optimization.[2] > > The Block GC, also known as the Block Chain GC, is an innovative new > system for Garbage Collection. It is a well-known fact that even though > the JVM can be fine-tuned to employ an optimal GC method for a specific > payload, most users do not bother to do so, or lack the technical skills > needed to select the proper GC. The Block GC is a "parasitic" GC, in > that it does not provide a separate GC system of it own, but instead > selects the most optimal GC for each individual payload. > > As a unique feature, the Block GC will measure and accurately calculate > the improvement provided by selecting the optimal GC method, compared to > the GC previously selected. Let T_gc_def be the time the user > application is stopped during the GC for the default GC settings, and > let T_gc_opt be the corresponding time using the optimal GC method > selected by the Block GC. The difference T_gc_def - T_gc_opt is the > improvement in pausetime provided by the Block GC, and is known as the > "block gain". > > The block gain can be seen as a hidden resource, available for free from > the user of the JRE. After the GC has finished, the JRE can use the time > provided by the block gain, with the user threads still suspended, > without the application suffering performance regressions. In the > initial implementation of the Block GC, the block gain was just used to > let the JVM sleep for an amount of time corresponding to the block gain. > This gave us a simple way to save processor cycles, and hence energy, > thus providing a simple way for the Java user to help fight climate > change without even noticing it. > > While a noble goal, this does not really makes business sense. In the > updated version of the Block GC, which we propose to be added as the > default GC in JDK 11, the block gain is instead used to calculate hash > values for popular cryptocurrencies, a.k.a. "bitcoin mining". Our > estimates show that this can generate a significant amount of revenue; > with a projected ~50 M downloads of JDK 11, running typical workloads, > and with typical values for GC settings (default or misconfigured), > $50k/day for all OpenJDK installations worldwide is not unreasonable. > > This is a pure win-win scenario. The user will not notice any > performance regression compared to the previous GC settings, and the > cryptocurrency account proprietor will benefit fiscally. > > The user can set their own blockchain account, instead of the default, > by issuing this command: > > java -XX:UnlockDangerousOptions > -XX:UnsupportedGCOption=new_provider_config: > > where points to a configuration file in ASN.1 > format describing the blockchain account. We hope to finish the > documentation of this file in time for the release, but if not done, it > will not be considered a release blocker. > > If a user override is not provided as above, by default, the revenue > extracted by the Block GC miner will be stored in the Block GC Project > account. This revenue will be divided as follows: 90% will go to the > initial committers of the Block GC Project, and 10% will go to the > OpenJDK community. > > The first installment of the 10% payment to the OpenJDK comminuty will > be issued exactly one year from now, on April 1st 2019.[3] > > A preview of the Block GC can be found here: > http://openjdk.java.net/preview/thisisunbelievable. > > The initial Committers will be: Magnus Ihse Bursie, Satoshi Nakamoto and > P. T. Barnum. > > /Magnus > > [1] http://openjdk.java.net/projects/#new-project > [2] http://openjdk.java.net/preview/thisisunbelievable > [3] https://en.wikipedia.org/wiki/April_Fools%27_Day > > From arjan.tijms at gmail.com Fri Apr 13 20:40:41 2018 From: arjan.tijms at gmail.com (arjan tijms) Date: Fri, 13 Apr 2018 21:40:41 +0100 Subject: Method and Field Literals In-Reply-To: References: Message-ID: Hi, >FWIW, method/field literals would be very useful for POJO-centric libraries > such as JPA/Hibernate, Bean Validation etc. Has there been any update on the method and field literals topic? Still something that would help a lot to reduce dependencies on string based programming. Kind regards, Arjan Tijms From stefan.karlsson at oracle.com Mon Apr 16 18:52:14 2018 From: stefan.karlsson at oracle.com (Stefan Karlsson) Date: Mon, 16 Apr 2018 20:52:14 +0200 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <98bcbdb3-681e-ec2b-dd36-1587dc5dd3d2@oracle.com> Vote: yes StefanK On 2018-04-16 20:32, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From omajid at redhat.com Mon Apr 16 19:45:43 2018 From: omajid at redhat.com (Omair Majid) Date: Mon, 16 Apr 2018 15:45:43 -0400 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <20180416194543.GD3138@redhat.com> Vote: Yes * Marcus Hirt [2018-04-16 14:42]: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. Cheers, Omair -- PGP Key: B157A9F0 (http://pgp.mit.edu/) Fingerprint = 9DB5 2F0B FD3E C239 E108 E7BD DF99 7AF8 B157 A9F0 From neugens.limasoftware at gmail.com Mon Apr 16 19:51:31 2018 From: neugens.limasoftware at gmail.com (Mario Torre) Date: Mon, 16 Apr 2018 21:51:31 +0200 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: Vote: Yes! Cheers, Mario 2018-04-16 20:32 GMT+02:00 Marcus Hirt : > * Mario Torres (Committer) Mario Torre ;) -- 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 poonam.bajaj at oracle.com Mon Apr 16 21:32:05 2018 From: poonam.bajaj at oracle.com (Poonam Parhar) Date: Mon, 16 Apr 2018 14:32:05 -0700 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <29fc4843-4bfb-77a7-d9b2-22db5153dc7f@oracle.com> Vote: yes Thanks, Poonam On 4/16/2018 11:32 AM, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From per.liden at oracle.com Mon Apr 16 22:04:11 2018 From: per.liden at oracle.com (Per Liden) Date: Tue, 17 Apr 2018 00:04:11 +0200 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <46d3ef3f-9b96-171d-970f-67334fa9a3ad@oracle.com> Vote: yes /Per On 04/16/2018 08:32 PM, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From stuart.marks at oracle.com Mon Apr 16 23:28:22 2018 From: stuart.marks at oracle.com (Stuart Marks) Date: Mon, 16 Apr 2018 16:28:22 -0700 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: Vote: yes On 4/16/18 11:32 AM, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From openjdk at haupz.de Tue Apr 17 06:19:33 2018 From: openjdk at haupz.de (Michael Haupt) Date: Tue, 17 Apr 2018 08:19:33 +0200 Subject: CFV: New Project: Mission Control In-Reply-To: <20180416194543.GD3138@redhat.com> References: <20180416194543.GD3138@redhat.com> Message-ID: Vote: yes (Yes please!) Michael > Am 16.04.2018 um 21:45 schrieb Omair Majid : > > Vote: Yes > > * Marcus Hirt [2018-04-16 14:42]: >> I hereby propose the creation of the Mission Control Project with myself >> (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > Cheers, > Omair > > -- > PGP Key: B157A9F0 (http://pgp.mit.edu/) > Fingerprint = 9DB5 2F0B FD3E C239 E108 E7BD DF99 7AF8 B157 A9F0 From volker.simonis at gmail.com Tue Apr 17 06:52:40 2018 From: volker.simonis at gmail.com (Volker Simonis) Date: Tue, 17 Apr 2018 08:52:40 +0200 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: Vote: yes On Mon, Apr 16, 2018 at 8:32 PM, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From dalibor.topic at oracle.com Tue Apr 17 07:12:39 2018 From: dalibor.topic at oracle.com (dalibor topic) Date: Tue, 17 Apr 2018 09:12:39 +0200 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <4fa0f465-5163-1eb4-40fd-adda9fc3e606@oracle.com> Vote: Yes! -- Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 ORACLE Deutschland B.V. & Co. KG | K?hneh?fe 5 | 22761 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 M?nchen Registergericht: Amtsgericht M?nchen, HRA 95603 Komplement?rin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Gesch?ftsf?hrer: Alexander van der Ven, Jan Schultheiss, Val Maher Oracle is committed to developing practices and products that help protect the environment From sean.coffey at oracle.com Tue Apr 17 07:28:30 2018 From: sean.coffey at oracle.com (=?UTF-8?Q?Se=c3=a1n_Coffey?=) Date: Tue, 17 Apr 2018 08:28:30 +0100 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: Vote: yes regards, Sean. On 16/04/2018 19:32, Marcus Hirt wrote: From roger.riggs at oracle.com Tue Apr 17 12:04:41 2018 From: roger.riggs at oracle.com (Roger Riggs) Date: Tue, 17 Apr 2018 08:04:41 -0400 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: Vote: Yes On 4/16/18 2:32 PM, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > From erik.helin at oracle.com Tue Apr 17 12:10:19 2018 From: erik.helin at oracle.com (Erik Helin) Date: Tue, 17 Apr 2018 14:10:19 +0200 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <99c0ce1e-d837-8f31-35dc-2d030be20798@oracle.com> Vote: yes Thanks, Erik On 04/16/2018 08:32 PM, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From thomas.stuefe at gmail.com Tue Apr 17 12:22:41 2018 From: thomas.stuefe at gmail.com (=?UTF-8?Q?Thomas_St=C3=BCfe?=) Date: Tue, 17 Apr 2018 14:22:41 +0200 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: Vote: yes! ..Thomas On Mon, Apr 16, 2018 at 8:32 PM, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From markus.gronlund at oracle.com Tue Apr 17 12:55:03 2018 From: markus.gronlund at oracle.com (Markus Gronlund) Date: Tue, 17 Apr 2018 05:55:03 -0700 (PDT) Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: Vote: yes Thanks Markus -----Original Message----- From: Marcus Hirt Sent: den 16 april 2018 20:32 To: announce at openjdk.java.net Subject: CFV: New Project: Mission Control I hereby propose the creation of the Mission Control Project with myself (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. In accordance with the OpenJDK guidelines [1], this project will provide a home for the continued development of the JDK Mission Control suite of tools, also known as JMC. JMC is a profiling and diagnostics tools suite for the JVM, primarily targeting systems running in production. JMC also provides independent bundles for parsing Java flight recordings, headless analysis of Java flight recordings, and more. We are now open-sourcing JMC to help keep the JVM-based languages in the absolute forefront in terms of production time profiling and diagnostics. Open sourcing the core libraries of JMC enables the Java ecosystem to quickly take advantage of features currently in the process of being open sourced in the JVM, such as the Java Flight Recorder, across all contemporary versions of Java. Open sourcing the stand alone JMC application will provide the community with a base suite of tooling for advanced JVM features, such as Java Flight Recorder. It will also provide the community with an opportunity to build upon this tooling to, for example, expand the number of IDEs supported, not to mention provide new features and capabilities. I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I have been working with Java and JVM technology since the early days of Java. I was one of the founders of Appeal Virtual Machines, and the original team leader of Java Mission Control. Many people have made significant contributions to Java Mission Control. Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who have been around for most of the journey. The initial Reviewers and Committers will be: * Marcus Hirt (Reviewer) * Klara Ward (Reviewer) * Ola Westin (Reviewer) * Henrik Dafg?rd (Reviewer) * Per Kroon (Reviewer) * Erik Greijus (Reviewer) * Erik Gahlin (Reviewer) * Guru Hb (Committer) * Suchita Chaturvedi (Committer) * Sharath Ballal (Committer) * David Buck (Committer) * Mario Torres (Committer) The initial source of this project will be based on the development branch of Mission Control 7. The final development and stabilization of Mission Control 7 will take place in the open. Change review policy will be determined by the Lead and a consensus of Reviewers. Review is expected to be relaxed initially, but made more strict as we get closer to the first release. The project will host at least the following mailing list: * jmc-dev for developers Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. Only current OpenJDK Members [1] are eligible to vote on this motion. Votes must be cast in the open on the discuss list. Replying to this message is sufficient if your mail program honors the Reply-To header. For Lazy Consensus voting instructions, see [2]. Kind regards, Marcus Hirt [1] http://openjdk.java.net/census#members [2] http://openjdk.java.net/projects/#new-project-vote From karen.kinnear at oracle.com Tue Apr 17 13:42:27 2018 From: karen.kinnear at oracle.com (Karen Kinnear) Date: Tue, 17 Apr 2018 09:42:27 -0400 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: Vote: yes thanks, Karen > On Apr 16, 2018, at 2:32 PM, Marcus Hirt wrote: > > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From adinn at redhat.com Tue Apr 17 14:01:38 2018 From: adinn at redhat.com (Andrew Dinn) Date: Tue, 17 Apr 2018 15:01:38 +0100 Subject: CFV: New Project: Mission Control In-Reply-To: <98bcbdb3-681e-ec2b-dd36-1587dc5dd3d2@oracle.com> References: <98bcbdb3-681e-ec2b-dd36-1587dc5dd3d2@oracle.com> Message-ID: <81da33ad-1847-902f-5de2-d4f68e7866de@redhat.com> Vote: yes 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 ChrisPhi at LGonQn.Org Tue Apr 17 14:09:16 2018 From: ChrisPhi at LGonQn.Org ("Chris Phillips"@T O) Date: Tue, 17 Apr 2018 10:09:16 -0400 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <9a99a4e8-c54b-9996-5e29-8a2f9900c9bf@LGonQn.Org> Vote: Yes Cheers! Chris From magnus.ihse.bursie at oracle.com Tue Apr 17 14:12:18 2018 From: magnus.ihse.bursie at oracle.com (Magnus Ihse Bursie) Date: Tue, 17 Apr 2018 16:12:18 +0200 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: Vote: yes /Magnus > 16 apr. 2018 kl. 20:32 skrev Marcus Hirt : > > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From vladimir.kozlov at oracle.com Tue Apr 17 16:21:05 2018 From: vladimir.kozlov at oracle.com (Vladimir Kozlov) Date: Tue, 17 Apr 2018 09:21:05 -0700 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <640e0b74-77e0-bf23-42c1-1a18be4ce867@oracle.com> Vote: yes On 4/16/18 11:32 AM, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From roman at kennke.org Tue Apr 17 16:25:05 2018 From: roman at kennke.org (Roman Kennke) Date: Tue, 17 Apr 2018 18:25:05 +0200 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <36c00247-8c50-1441-a86a-f42a17d7e8ae@kennke.org> Vote: yes > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > > From david.holmes at oracle.com Tue Apr 17 20:58:00 2018 From: david.holmes at oracle.com (David Holmes) Date: Wed, 18 Apr 2018 06:58:00 +1000 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: Vote: yes David ------ On 17/04/2018 4:32 AM, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From mandy.chung at oracle.com Wed Apr 18 01:32:07 2018 From: mandy.chung at oracle.com (mandy chung) Date: Wed, 18 Apr 2018 09:32:07 +0800 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: Vote: yes Mandy From maurizio.cimadamore at oracle.com Wed Apr 18 01:33:17 2018 From: maurizio.cimadamore at oracle.com (Maurizio Cimadamore) Date: Tue, 17 Apr 2018 18:33:17 -0700 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <49cce0b6-bf87-90b7-c8af-7bd21617e43d@oracle.com> Vote: yes! Maurizio On 16/04/18 11:32, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From laurent.daynes at oracle.com Wed Apr 18 06:50:35 2018 From: laurent.daynes at oracle.com (Laurent Daynes) Date: Wed, 18 Apr 2018 08:50:35 +0200 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <43bd274d-6738-8118-261b-03f6b5889fdd@oracle.com> Vote: yes Laurent Le 16/04/2018 ? 20:32, Marcus Hirt a ?crit?: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From daniel.fuchs at oracle.com Wed Apr 18 10:49:59 2018 From: daniel.fuchs at oracle.com (Daniel Fuchs) Date: Wed, 18 Apr 2018 11:49:59 +0100 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <9cfaf6cb-e1a2-1f63-f774-abb627383848@oracle.com> Vote: yes -- daniel On 16/04/2018 19:32, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. From Sergey.Bylokhov at oracle.com Wed Apr 18 15:09:00 2018 From: Sergey.Bylokhov at oracle.com (Sergey Bylokhov) Date: Wed, 18 Apr 2018 08:09:00 -0700 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: Vote: yes On 16/04/2018 11:32, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > -- Best regards, Sergey. From coleen.phillimore at oracle.com Wed Apr 18 18:36:58 2018 From: coleen.phillimore at oracle.com (coleen.phillimore at oracle.com) Date: Wed, 18 Apr 2018 14:36:58 -0400 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <57d96a62-22e8-9603-f1ee-b6930ec61a54@oracle.com> Vote: yes On 4/16/18 2:32 PM, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From shade at redhat.com Thu Apr 19 10:32:19 2018 From: shade at redhat.com (Aleksey Shipilev) Date: Thu, 19 Apr 2018 12:32:19 +0200 Subject: CFV: New Project: Mission Control In-Reply-To: <98bcbdb3-681e-ec2b-dd36-1587dc5dd3d2@oracle.com> References: <98bcbdb3-681e-ec2b-dd36-1587dc5dd3d2@oracle.com> Message-ID: <8bbf3264-4204-29b6-5bc1-d98fb4eb890d@redhat.com> Vote: yes On 2018-04-16 20:32, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. -Aleksey From list at xenhideout.nl Mon Apr 23 10:14:35 2018 From: list at xenhideout.nl (Xen) Date: Mon, 23 Apr 2018 12:14:35 +0200 Subject: JNI crashes JVM (from C) -- openjdk 8 Message-ID: <205d323cd935ed28831915f8636b24af@xenhideout.nl> Hi, I am new to using JNI but I don't know where I can get any help. On my openjdk-8 Linux system, the example at https://docs.oracle.com/javase/8/docs/technotes/guides/jni/spec/invocation.html is in C++ but when run the GetStaticMethodID call crashes the JVM. However when I change it to C, already the FindClass call crashes the JVM. This fragment includes JavaVM *jvm; /* denotes a Java VM */ JNIEnv *env; /* pointer to native method interface */ in C++, in C I change it to JavaVM *jvm; JNIEnv env; to make it compile. I compile with include dirs of /usr/lib/jvm/java-8-openjdk-amd64/include and /usr/lib/jvm/java-8-openjdk-amd64/include/linux And link with /usr/lib/jvm/java-8-openjdk-amd64/jre/lib /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/server and test.c -ljava -ljvm Consequently, I run with LD_LIBRARY_PATH=...:... with those values. The program runs, but there is always a JVM crash. I was surprised to see it pass the FindClass call with C++. I have not tested other JDKs or JREs. The Main class is as simple as it gets, as per the example: public class Main { public static void test(int i) { System.out.println(i); } } But honestly, the C version always crashes the JVM, no matter what class I give it; even non-existent classes always crash it. I can attach verbosity (-verbose:jni) but it lists no errors anywhere; or -Xcheck:jni, but that doesn't change the output. I can attach the complete output, but I was wondering if this is a known issue? Am I doing something wrong? This is Oracle's minimal example; the code compiles and can find everything. #include /* where everything is defined */ int main() { JavaVM *jvm; /* denotes a Java VM */ JNIEnv env; /* pointer to native method interface */ JavaVMInitArgs vm_args; /* JDK/JRE 6 VM initialization arguments */ JavaVMOption options[1]; options[0].optionString = "-Djava.class.path=/usr/lib/java"; vm_args.version = JNI_VERSION_1_6; vm_args.nOptions = 1; vm_args.options = options; vm_args.ignoreUnrecognized = 0; /* load and initialize a Java VM, return a JNI interface * pointer in env */ JNI_CreateJavaVM(&jvm, (void**)&env, &vm_args); /* invoke the Main.test method using the JNI */ jclass cls = env->FindClass(&env, "Main"); // <--- C crashes here jmethodID mid = env->GetStaticMethodID(&env, cls, "test", "(I)V"); // <--- C++ here env->CallStaticVoidMethod(cls, mid, 100); // <--- never reached /* We are done. */ (*jvm)->DestroyJavaVM(jvm); } I have tested this on CentOS 7.4 as well, with versions 1.8.0, 1.7.0 and 1.6.0, all giving the same error messages: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x0000000000000000, pid=24945, tid=0x00007f5eeab0f740 # # JRE version: OpenJDK Runtime Environment (8.0_161-b14) (build 1.8.0_161-b14) # Java VM: OpenJDK 64-Bit Server VM (25.161-b14 mixed mode linux-amd64 compressed oops) # Problematic frame: # C 0x0000000000000000 The others are the same. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: hs_err_pid25637.log URL: From martijnverburg at gmail.com Mon Apr 23 10:35:09 2018 From: martijnverburg at gmail.com (Martijn Verburg) Date: Mon, 23 Apr 2018 11:35:09 +0100 Subject: JNI crashes JVM (from C) -- openjdk 8 In-Reply-To: <205d323cd935ed28831915f8636b24af@xenhideout.nl> References: <205d323cd935ed28831915f8636b24af@xenhideout.nl> Message-ID: Hi there, Welcome to OpenJDK! The discuss list is more for discussion around OpenJDK (the project and community). I'd recommend joining adoption-discuss for asking questions if you're new to OpenJDK. Stackoverflow is also a popular resource for these sorts of questions. Cheers, Martijn On 23 April 2018 at 11:14, Xen wrote: > Hi, > > I am new to using JNI but I don't know where I can get any help. > > On my openjdk-8 Linux system, the example at > https://docs.oracle.com/javase/8/docs/technotes/guides/jni/ > spec/invocation.html > > is in C++ but when run the GetStaticMethodID call crashes the JVM. > > However when I change it to C, already the FindClass call crashes the JVM. > > This fragment includes > > JavaVM *jvm; /* denotes a Java VM */ > JNIEnv *env; /* pointer to native method interface */ > > in C++, in C I change it to > > JavaVM *jvm; > JNIEnv env; > > to make it compile. > > I compile with include dirs of > > /usr/lib/jvm/java-8-openjdk-amd64/include and > /usr/lib/jvm/java-8-openjdk-amd64/include/linux > > And link with > > /usr/lib/jvm/java-8-openjdk-amd64/jre/lib > /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/server > > and test.c -ljava -ljvm > > Consequently, I run with LD_LIBRARY_PATH=...:... with those values. > > The program runs, but there is always a JVM crash. I was surprised to see > it pass the FindClass call with C++. > > I have not tested other JDKs or JREs. > > The Main class is as simple as it gets, as per the example: > > public class Main { > public static void test(int i) { > System.out.println(i); > } > } > > But honestly, the C version always crashes the JVM, no matter what class I > give it; even non-existent classes always crash it. > > I can attach verbosity (-verbose:jni) but it lists no errors anywhere; or > -Xcheck:jni, but that doesn't change the output. > > I can attach the complete output, but I was wondering if this is a known > issue? > > Am I doing something wrong? > > This is Oracle's minimal example; the code compiles and can find > everything. > > #include /* where everything is defined */ > > int main() { > JavaVM *jvm; /* denotes a Java VM */ > JNIEnv env; /* pointer to native method interface */ > JavaVMInitArgs vm_args; /* JDK/JRE 6 VM initialization arguments */ > JavaVMOption options[1]; > options[0].optionString = "-Djava.class.path=/usr/lib/java"; > vm_args.version = JNI_VERSION_1_6; > vm_args.nOptions = 1; > vm_args.options = options; > vm_args.ignoreUnrecognized = 0; > /* load and initialize a Java VM, return a JNI interface > * pointer in env */ > > JNI_CreateJavaVM(&jvm, (void**)&env, &vm_args); > > /* invoke the Main.test method using the JNI */ > > jclass cls = env->FindClass(&env, "Main"); // <--- C > crashes here > jmethodID mid = env->GetStaticMethodID(&env, cls, "test", "(I)V"); > // <--- C++ here > env->CallStaticVoidMethod(cls, mid, 100); // <--- never > reached > /* We are done. */ > (*jvm)->DestroyJavaVM(jvm); > } > > > > I have tested this on CentOS 7.4 as well, with versions 1.8.0, 1.7.0 and > 1.6.0, all giving the same error messages: > > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x0000000000000000, pid=24945, > tid=0x00007f5eeab0f740 > # > # JRE version: OpenJDK Runtime Environment (8.0_161-b14) (build > 1.8.0_161-b14) > # Java VM: OpenJDK 64-Bit Server VM (25.161-b14 mixed mode linux-amd64 > compressed oops) > # Problematic frame: > # C 0x0000000000000000 > > The others are the same. From list at xenhideout.nl Mon Apr 23 13:30:53 2018 From: list at xenhideout.nl (Xen) Date: Mon, 23 Apr 2018 15:30:53 +0200 Subject: JNI crashes JVM (from C) -- openjdk 8 In-Reply-To: References: <205d323cd935ed28831915f8636b24af@xenhideout.nl> Message-ID: <4daa3f185a9d1028ff32733109994199@xenhideout.nl> Martijn Verburg schreef op 23-04-2018 12:35: > Hi there, > > Welcome to OpenJDK! The discuss list is more for discussion around > OpenJDK (the project and community). I'd recommend joining > adoption-discuss for asking questions if you're new to OpenJDK. > Stackoverflow is also a popular resource for these sorts of questions. > > Cheers, > Martijn Hi Martijn, I will try adoption-discuss. StackOverflow is not my cup of tea ;-). Regards. From list at xenhideout.nl Mon Apr 23 14:12:51 2018 From: list at xenhideout.nl (Xen) Date: Mon, 23 Apr 2018 16:12:51 +0200 Subject: JNI crashes JVM (from C) -- openjdk 8 In-Reply-To: References: <205d323cd935ed28831915f8636b24af@xenhideout.nl> Message-ID: <4c1273b5ef7e559ce127d673e5566a16@xenhideout.nl> Martijn Verburg schreef op 23-04-2018 12:35: > Hi there, > > Welcome to OpenJDK! The discuss list is more for discussion around > OpenJDK (the project and community). I'd recommend joining > adoption-discuss for asking questions if you're new to OpenJDK. > Stackoverflow is also a popular resource for these sorts of questions. Hi thanks, I solved my problem. Call it lack of C++ expertise on my side. (Couldn't understand why C++ was okay with env->method but C wanted (*env)->method, even though both were already pointers...). I had made an error in the (void **)&env, which, due to the nature of the void cast, hadn't resulted in a compiler error so I thought I was good ;-). Ah, the convoluted nature of trees! ;-). Regards, and thanks. From daniel.daugherty at oracle.com Tue Apr 17 18:09:15 2018 From: daniel.daugherty at oracle.com (Daniel D. Daugherty) Date: Tue, 17 Apr 2018 14:09:15 -0400 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <62e2bf94-1024-e86e-fd6e-d99880c0b32a@oracle.com> Vote: Yes! Dan On 4/16/18 2:32 PM, Marcus Hirt wrote: > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > > From jesper.wilhelmsson at oracle.com Mon Apr 23 20:50:35 2018 From: jesper.wilhelmsson at oracle.com (jesper.wilhelmsson at oracle.com) Date: Mon, 23 Apr 2018 22:50:35 +0200 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <649C709F-FD46-434A-B34E-8BF3D67BAFE3@oracle.com> Vote: Yes /Jesper > On 16 Apr 2018, at 20:32, Marcus Hirt wrote: > > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > > From jhg023 at bucknell.edu Sun Apr 29 18:24:22 2018 From: jhg023 at bucknell.edu (Jacob Glickman) Date: Sun, 29 Apr 2018 14:24:22 -0400 Subject: Hello! Message-ID: Hello! My name is Jacob, and I just joined as an OpenJDK contributor the other day. I have a plethora of ideas regarding new methods to add to existing APIs; however, I'm not entirely sure how to go about proposing them (or, at least, *where* to propose them). Specifically, I was looking for the mailing list that covers Java's Collections API, but I'm not sure which one that would be (if I had to guess, it would be jdk-dev). I've read over the "How to Contribute" page as well, but I'm still confused regarding how to build the JDK (or even where to get the files from to make changes). If anyone could provide me with some tips that helped them when they joined, I would be very grateful! Hopefully the formatting of this on the mailing list doesn't look that bad! - Jacob From martijnverburg at gmail.com Mon Apr 30 17:11:11 2018 From: martijnverburg at gmail.com (Martijn Verburg) Date: Mon, 30 Apr 2018 18:11:11 +0100 Subject: Hello! In-Reply-To: References: Message-ID: Hi Jacob and welcome to OpenJDK! I'd recommend joining adoption-discuss and posting your question there. We'll get you started on how you can best contribute to OpenJDK! Cheers, Martijn On 29 April 2018 at 19:24, Jacob Glickman wrote: > Hello! My name is Jacob, and I just joined as an OpenJDK contributor the > other day. I have a plethora of ideas regarding new methods to add to > existing APIs; however, I'm not entirely sure how to go about proposing > them (or, at least, *where* to propose them). Specifically, I was looking > for the mailing list that covers Java's Collections API, but I'm not sure > which one that would be (if I had to guess, it would be jdk-dev). I've > read over the "How to Contribute" page as well, but I'm still confused > regarding how to build the JDK (or even where to get the files from to make > changes). If anyone could provide me with some tips that helped them when > they joined, I would be very grateful! > > Hopefully the formatting of this on the mailing list doesn't look that bad! > > - Jacob > From cthalinger at twitter.com Mon Apr 30 18:09:05 2018 From: cthalinger at twitter.com (Christian Thalinger) Date: Mon, 30 Apr 2018 20:09:05 +0200 Subject: CFV: New Project: Mission Control In-Reply-To: References: Message-ID: <4721BE7B-AEF2-470E-B1AD-B260FC55F73C@twitter.com> Vote: yes > On Apr 16, 2018, at 8:32 PM, Marcus Hirt wrote: > > I hereby propose the creation of the Mission Control Project with myself > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group. > > In accordance with the OpenJDK guidelines [1], this project will provide > a home for the continued development of the JDK Mission Control suite of > tools, also known as JMC. JMC is a profiling and diagnostics tools suite > for the JVM, primarily targeting systems running in production. JMC also > provides independent bundles for parsing Java flight recordings, headless > analysis of Java flight recordings, and more. > > We are now open-sourcing JMC to help keep the JVM-based languages > in the absolute forefront in terms of production time profiling and > diagnostics. > > Open sourcing the core libraries of JMC enables the Java ecosystem to > quickly take advantage of features currently in the process of being > open sourced in the JVM, such as the Java Flight Recorder, across all > contemporary versions of Java. > > Open sourcing the stand alone JMC application will provide the community > with a base suite of tooling for advanced JVM features, such as Java > Flight Recorder. It will also provide the community with an opportunity > to build upon this tooling to, for example, expand the number of IDEs > supported, not to mention provide new features and capabilities. > > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I > have been working with Java and JVM technology since the early days of > Java. I was one of the founders of Appeal Virtual Machines, and the > original team leader of Java Mission Control. > > Many people have made significant contributions to Java Mission Control. > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who > have been around for most of the journey. > > The initial Reviewers and Committers will be: > > * Marcus Hirt (Reviewer) > * Klara Ward (Reviewer) > * Ola Westin (Reviewer) > * Henrik Dafg?rd (Reviewer) > * Per Kroon (Reviewer) > * Erik Greijus (Reviewer) > * Erik Gahlin (Reviewer) > * Guru Hb (Committer) > * Suchita Chaturvedi (Committer) > * Sharath Ballal (Committer) > * David Buck (Committer) > * Mario Torres (Committer) > > The initial source of this project will be based on the development branch > of Mission Control 7. The final development and stabilization of Mission > Control 7 will take place in the open. Change review policy will be determined > by the Lead and a consensus of Reviewers. Review is expected to be relaxed > initially, but made more strict as we get closer to the first release. > > The project will host at least the following mailing list: > > * jmc-dev for developers > > Votes are due by 23:59 CET on Tuesday the 1st of May, 2018. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > Kind regards, > Marcus Hirt > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > >