payload: {"action":"created","issue":{"url":"https://api.github.com/repos/eclipse/openj9/issues/6203","repository_url":"https://api.github.com/repos/eclipse/openj9","labels_url":"https://api.github.com/repos/eclipse/openj9/issues/6203/labels{/name}","comments_url":"https://api.github.com/repos/eclipse/openj9/issues/6203/comments","events_url":"https://api.github.com/repos/eclipse/openj9/issues/6203/events","html_url":"https://github.com/eclipse/openj9/issues/6203","id":458683011,"node_id":"MDU6SXNzdWU0NTg2ODMwMTE=","number":6203,"title":"Deciding on a replacing name for JITaaS","user":{"login":"mpirvu","id":22594880,"node_id":"MDQ6VXNlcjIyNTk0ODgw","avatar_url":"https://avatars1.githubusercontent.com/u/22594880?v=4","gravatar_id":"","url":"https://api.github.com/users/mpirvu","html_url":"https://github.com/mpirvu","followers_url":"https://api.github.com/users/mpirvu/followers","following_url":"https://api.github.com/users/mpirvu/following{/other_user}","gists_url":"https://api.github.com/users/mpirvu/gists{/gist_id}","starred_url":"https://api.github.com/users/mpirvu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mpirvu/subscriptions","organizations_url":"https://api.github.com/users/mpirvu/orgs","repos_url":"https://api.github.com/users/mpirvu/repos","events_url":"https://api.github.com/users/mpirvu/events{/privacy}","received_events_url":"https://api.github.com/users/mpirvu/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":24,"created_at":"2019-06-20T14:12:17Z","updated_at":"2019-06-27T17:17:18Z","closed_at":"2019-06-27T17:17:18Z","author_association":"CONTRIBUTOR","body":"@mstoodle  brought to my attention that `JITaaS` can be easily mispronounced and therefore we need to find a better name. This issue serves as a discussion forum for coming up with a replacement.\r\n\r\nCurrently, `JITaaS` is used in:\r\n1) Filenames. E.g.: JITaaSCompilationThread.cpp, JITaaSPersistentCHTable.cpp\r\n2) Namespaces\r\n3) Data structures. E.g.: JITaaSHelpers, JITaaSPersistentClassInfo, JITaaSIProfiler\r\n4) vlog and error messages\r\n5) Name of options: -XX:JITaaSClient\r\n6) Soon to come, #ifdefs\r\n\r\nA grep over the code base shows ~1500 hits.\r\n\r\nAlternate names being proposed:\r\n- JITservice\r\n- JITsrvc\r\n- JITserv\r\n- OopJIT (from out-of-process JIT)\r\n- RemoteJIT\r\n\r\nThe list is still open!"},"comment":{"url":"https://api.github.com/repos/eclipse/openj9/issues/comments/506434897","html_url":"https://github.com/eclipse/openj9/issues/6203#issuecomment-506434897","issue_url":"https://api.github.com/repos/eclipse/openj9/issues/6203","id":506434897,"node_id":"MDEyOklzc3VlQ29tbWVudDUwNjQzNDg5Nw==","user":{"login":"mpirvu","id":22594880,"node_id":"MDQ6VXNlcjIyNTk0ODgw","avatar_url":"https://avatars1.githubusercontent.com/u/22594880?v=4","gravatar_id":"","url":"https://api.github.com/users/mpirvu","html_url":"https://github.com/mpirvu","followers_url":"https://api.github.com/users/mpirvu/followers","following_url":"https://api.github.com/users/mpirvu/following{/other_user}","gists_url":"https://api.github.com/users/mpirvu/gists{/gist_id}","starred_url":"https://api.github.com/users/mpirvu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mpirvu/subscriptions","organizations_url":"https://api.github.com/users/mpirvu/orgs","repos_url":"https://api.github.com/users/mpirvu/repos","events_url":"https://api.github.com/users/mpirvu/events{/privacy}","received_events_url":"https://api.github.com/users/mpirvu/received_events","type":"User","site_admin":false},"created_at":"2019-06-27T17:17:18Z","updated_at":"2019-06-27T17:17:18Z","author_association":"CONTRIBUTOR","body":"Since no other opinions were expressed we will proceed with changing `JITaaS` into `JITServer` throughout the code.\r\n\r\nPublic options will be\r\n`-XX:+StartAsJitServer` to activate the JVM as a JIT server\r\n`-XX:+UseJitServer` to allow the JVM to send remote compilation requests\r\n\r\n@smlambert when we change the options and deliver them to master we need to address the testing infrastructure.\r\n\r\nThank you all for your input on this matter!"}}
other: {"actor":{"display_login":"mpirvu"}}