CFV: Project Portola
volker.simonis at gmail.com
Thu Feb 23 10:05:51 UTC 2017
As you can see from my vote, I'm all for this project, but I have
several comments and questions:
1. According to the OpenJDK guide lines "It is recommended (and I'd
consider it "good style") that any proposal for a new Project be
discussed publicly before being proposed for a vote. I haven't seen
such a discussion :)
2. What is the scope of this "port" - will it be considered as a new
OS or will it be handled as a "linux" flavor?
3. Which architectures will be supported? From a quick look at the
"musl" page I saw that s390 is not supported and aarch64 support is
Thank you and best regards,
On Wed, Feb 22, 2017 at 7:17 PM, Mikael Vidstedt
<mikael.vidstedt at oracle.com> wrote:
> I hereby propose the creation of Project Portola with myself as the
> Lead and the Porters group as the sponsoring group.
> This Project will provide a port of the JDK to the Alpine Linux 
> distribution, and in particular the "musl" C library .
> About the Lead: Mikael Vidstedt (OpenJDK username: mikael) is a JDK 9
> Committer, and also a Committer in the Panama project where he has
> been working on providing significantly improved support for
> foreign/native data and function access. He is working in the Hotspot
> team at Oracle, and has been working with JVMs for more than 15 years.
> The initial Reviewers and Committers will be:
> Mikael Vidstedt
> David Holmes
> Erik Joelsson
> Kumar Srinivasan
> Alan Bateman
> Vladimir Kozlov
> Sangheon Kim
> Poonam Bajaj
> Jini George
> The project will host at least the following mailing list:
> * portola-dev for development discussions and user feedback
> The initial source of this project will be based on a clone of a JDK
> 10 repository. Changes from the JDK 10 parent will be synced into
> Portola periodically. Similar to Projects Lambda and Valhalla, we will
> follow a "commit first, review later" policy, as code will not flow
> directly from the Portola repositories into the JDK repositories, but
> instead will be done by a "curated merge" where select changes are
> extracted into new changesets for incorporation into JDK repositories
> when they are ready for inclusion.
> Votes are due by March 8, 2017.
> Only current OpenJDK Members  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 .
>  https://www.alpinelinux.org
>  http://www.musl-libc.org
>  http://openjdk.java.net/census#members
>  http://openjdk.java.net/projects/#new-project-vote
More information about the discuss