From john.r.rose at oracle.com Wed Jun 4 05:19:12 2014 From: john.r.rose at oracle.com (John Rose) Date: Tue, 3 Jun 2014 22:19:12 -0700 Subject: CFV: New Project: Panama Message-ID: <7233125D-21CB-4192-BFEB-E7AAAA05D5D2@oracle.com> I hereby propose the creation of Project Panama with myself (John Rose) as the Lead and the HotSpot Group as the sponsoring Group. In accordance with the OpenJDK guidelines [1], this project will provide new connections between the Java virtual machine and well-defined but "foreign" (non-Java) APIs, including many interfaces commonly used by C programmers. The project will provide an venue to incubate early work on JEP 191[2] and similar enhancements, as discussed on my blog[3]. In short, the components developed in this project will support: * native code and data access between the JVM and native APIs * tooling for header file API extraction and API metadata storage * wrapper interposition for specialized safety invariants and value transformations * basic bindings for selected native APIs The initial source of this project will be based on a clone of a JDK 9 repository, most specifically the hotspot, langtools, and jdk sub-repositories. We also plan (with appropriate permissions) to make use of certain software components mentioned in JEP 191. To host components which may not immediately fit into the existing repository structure, there will also be a "scratch" repository modeled on that of Sumatra[4]. The initial Reviewers and Committers will be: * David Chase (Reviewer, HotSpot/compiler) * Mandy Chung (Reviewer, Core Libraries) * Mike Duigou (Reviewer, Core Libraries) * Vladimir Ivanov (Reviewer, HotSpot/compiler) * Henry Jen (Committer, Core Libraries) * Wayne Meissner (Committer, libffi/JNR) * Charles Nutter (Reviewer, JRuby/JNR) * Paul Sandoz (Committer, Core Libraries) * David Simms (Committer, HotSpot/runtime) * Attila Szegedi (Reviewer, Language Tools) * Chris Thalinger (Reviewer, HotSpot/compiler) * Bob Vandette (Reviewer, HotSpot/embedded) (In parentheses are their prospective Panama role and a current OpenJDK or other affiliation. Reviewer status is assigned based on previous review history. Note that, per OpenJDK requirements[5], authoring for this project requires a filed Oracle Contributor Agreement.) The project will maintain at least two mailing lists: * panama-dev for developers (as usual) * panama-spec-experts for specification issues only For widest discussion of standardization questions, the specification mailing list, distinct from the developer list, may include participants from the Java Community Process who are not OpenJDK contributors. This list will exclude discussion of implementation code, and may be moderated or otherwise restricted to meet this goal. Change review will be determined by the Lead and a consensus of Reviewers. Review is expected to be loose initially but made more strict, perhaps on a per-component basis as components become candidates for integration into Java SE releases such as JDK 9. Votes are due in two weeks, by 12:00 midnight June 18 2014 Pacific US Time (18-06-2014 07:00 GMT). Only current OpenJDK Members [6] 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 [7]. Regards, John Rose [1] http://openjdk.java.net/projects/#new-project [2] http://openjdk.java.net/jeps/191 [3] https://blogs.oracle.com/jrose/entry/the_isthmus_in_the_vm [4] http://hg.openjdk.java.net/sumatra/sumatra-dev/scratch/ [5] http://openjdk.java.net/contribute/ [6] http://openjdk.java.net/census#members [7] http://openjdk.java.net/projects/#new-project-vote From mark.reinhold at oracle.com Wed Jun 18 15:42:01 2014 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Wed, 18 Jun 2014 08:42:01 -0700 Subject: New mailing list: platform-jep-discuss Message-ID: <20140618084201.5486@eggemoggin.niobe.net> As proposed in the JEP 2.0 draft [1], I've created a new mailing list where large, cross-component JEPs can be discussed until such time as they have Project-specific mailing lists. Here's the list description in Mailman: This list hosts early discussions of large, cross-component JEPs. Such a JEP, when first drafted, may direct readers to use this list for initial discussions. This list may continue to be used until such time as further discussion of that JEP can be hosted in a list associated with an appropriate OpenJDK Group or Project. This list is not intended for the discussion of arbitrary feature proposals; it is solely for the discussion of existing JEP documents. Like most OpenJDK mailing lists, anyone may subscribe to this list, but only subscribers may post. To subscribe: http://mail.openjdk.java.net/mailman/listinfo/platform-jep-discuss - Mark [1] http://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html From brian.goetz at oracle.com Sun Jun 22 15:05:40 2014 From: brian.goetz at oracle.com (Brian Goetz) Date: Sun, 22 Jun 2014 11:05:40 -0400 Subject: CFV: Project Valhalla Message-ID: <53A6F0C4.8020907@oracle.com> I hereby propose the creation of Project Valhalla with myself as the Lead and the HotSpot group as the sponsoring group. In accordance with the OpenJDK guidelines [1], this project will provide a venue to explore and incubate advanced Java VM and Language feature candidates such as Value Types [2], Generic Specialization [3], enhanced volatiles [4] (and possibly other related topics, such as reified generics.) The initial Reviewers and Committers will be: * Brian Goetz * John Rose * Paul Sandoz * Maurizio Cimadamore * Paul Govereau * Dan Smith * David Chase * Mike Duigou * Vladimir Ivanov * Albert Noll The project will host at least the following mailing list: * valhalla-dev for developers and may eventually host specification lists if one or more JSRs is subsequently created. The initial source of this project will be based on a clone of a JDK 9 repository. Changes from the JDK 9 parent will be synced into Valhalla periodically. Similar to Project Lambda, we will follow a "commit first, review later" policy, as code will not flow directly from the Valhalla 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 July 7, 2014, 9A GMT. Only current OpenJDK Members [5] 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 [6]. [1] http://openjdk.java.net/projects/#new-project [2] http://cr.openjdk.java.net/~jrose/values/values-0.html [3] https://bugs.openjdk.java.net/browse/JDK-8046267 [4] http://openjdk.java.net/jeps/193 [5] http://openjdk.java.net/census#members [6] http://openjdk.java.net/projects/#new-project-vote From john.r.rose at oracle.com Mon Jun 23 20:23:04 2014 From: john.r.rose at oracle.com (John Rose) Date: Mon, 23 Jun 2014 15:23:04 -0500 Subject: Result: New Project: Panama Message-ID: <63A0CDCE-EE00-40EE-B2A1-66C1D7F963FF@oracle.com> Voting for Project Panama [1] is now closed. Yes: 19 Veto: 0 Abstain: 0 According to the Bylaws definition of Lazy Consensus [2], this is sufficient to approve the creation of this project. ? John P.S. This is a resend with corrected subject line. [1] http://mail.openjdk.java.net/pipermail/announce/2014-June/000172.html [2] http://openjdk.java.net/bylaws#lazy-consensus From jonathan.gibbons at oracle.com Fri Jun 27 20:45:00 2014 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Fri, 27 Jun 2014 13:45:00 -0700 Subject: CFV: Project Annotations Pipeline 2.0 Message-ID: <53ADD7CC.6050507@oracle.com> JDK 8 saw the introduction of three separate language features affecting annotations and annotation processing. * Annotations on Java Types [1] * Repeating Annotations [2] * Lambda Expressions [3], which introduced new positions for annotations Although these features were developed independently, there is non-trivial overlap between them, such as repeated type annotations on a parameter type in a lambda expression. In addition, these features all have to work well together with existing features such as the Annotation Processing API, Language Model API, and javadoc. The machinery within javac to handle these features needs to be improved. Therefore, I hereby propose the creation of Project Annotations Pipeline 2.0 with Joel Borggr?n-Franck as the Lead and the Compiler group as the sponsoring group. In accordance with the OpenJDK guidelines [4], this project will provide a venue to explore improvements to the overall handling of annotations within the javac compilation pipeline. The project will be entirely focussed on improving the implementation of the existing language and API specifications, and is not intended as a venue to change or enhance these specifications. The initial Reviewers and Committers will be: * Jonathan Gibbons * Joel Borggr?n-Franck * Maurizio Cimadamore * Eric McCorkle * Jan Lahoda * Alex Buckley Initial Authors will be * Werner Dietl * Steve Sides * Andrey Eremeev The project will host the following mailing list for developers: * anno-pipeline-dev The initial source of this project will be based on a clone of a JDK 9 repository. Changes from the JDK 9 parent will be synced into Annotations Pipeline 2.0 periodically. Similar to Project Lambda, we will follow a "commit first, review later" policy, as code will not flow directly from the Annotations Pipeline 2.0 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 July 11, 2014, 5PM PDT. Only current OpenJDK Members [5] 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 [6]. [1] https://www.jcp.org/en/jsr/detail?id=308 [2] http://openjdk.java.net/jeps/120 [3] https://jcp.org/en/jsr/detail?id=335 [4] http://openjdk.java.net/projects/#new-project [5] http://openjdk.java.net/census#members [6] http://openjdk.java.net/projects/#new-project-vote