From aoqi at loongson.cn Thu Jul 26 16:01:46 2018 From: aoqi at loongson.cn (Ao Qi) Date: Fri, 27 Jul 2018 00:01:46 +0800 Subject: Current Status of OpenJDK 8 for mips64el In-Reply-To: References: <4093f9b9-2159-e4c0-9359-fd5f66c9ec46@oracle.com> Message-ID: Hi Dalibor, Ping? Could you suggest me what should I do for bringing the port into the MIPS Porting Project? Thanks, Ao Qi Ao Qi ?2018?6?19??? ??4:28??? > > > > > Hi, > > > > I think that it's too late for a new a port come into JDK 8 Updates Project > > at this time, with less then a year to go under the current maintainers, > > considering how long it would take to bring the code into OpenJDK, run > > through the JEP process, code reviews, etc. > > > > It's probably too late for a fresh port to make it into JDK 11, as well, > > with less than a month to go until rampdown starts. > > > > Thank you very much for your reply and suggestion. I understand that > it is too late for a new port to be into the main line of jdk8u and > jdk11. > > > So my suggestion would be to start by bringing your port into the MIPS > > Porting Project, and then, once it's brought forward to JDK 11 and there is > > a build passing JCK for Java SE 11, to go through the JEP process for > > inclusion in a later version of the JDK. > > > > I think your suggestion is very reasonable, helpful and acceptable. We > are willing to adopt your suggestion. However, I have one question > about your suggestion. Could you explain more about bringing our port > into the MIPS Porting Project? I'm not quite sure what it specifically > means. Is that we can put our code into OpenJDK repository (not the > main line) like aarh64 jdk8u[1] and the further development should > happened according to community requirements, such as [2][3]? > > [1] http://hg.openjdk.java.net/aarch64-port > [2] http://openjdk.java.net/bylaws > [3] http://openjdk.java.net/contribute > > > cheers, > > dalibor topic > > > >>