The Java Community Process Program Management Office (PMO) and Executive Committees (EC) today launched JCP 2.6, the most transparent and accessible iteration in the program’s evolution to date. The process enhancements give earlier access to draft specifications to a broader group of developers and add more value at each level of participation. This makes it easier and more rewarding for developers to get involved in the Java technology standards definition process.

Effective immediately, the changes are defined in the final release of the Java Specification Request (JSR) 215 and in the new Java Process Document, at Specifications currently subject to version 2.5 will be able to automatically take full advantage of the new JCP process.

JCP 2.6 better services developer needs by adding new efficiencies to the process:

*sets the stage for both JCP and non JCP members to contribute their input to an early review JSR cycle creating a more open and inclusive community;

*provides Spec Leads with new processes and tools which make it easier for them to drive more accessible JSRs and better communicate information about specifications to the entire Java community;

*encourages Spec Leads to enter review periods sooner, enabling a more efficient process and results that benefit from a broad public input.
With this program refresh the JCP demonstrates once again its members’ commitment to to evolve the process into the best community-based environment for Java technology innovation and the most successful binary standards body in the industry.

“The JCP is constantly improving itself to meet the needs of the Java community, and JCP 2.6 is an important step in that evolution,” said Aaron Williams, specification lead for JSR 215 and JCP Executive Relations manager. “By creating more transparency into the Expert Groups, and opening the drafts earlier and to a wider audience, we are encouraging more participation in the community and results that are more widely adopted. We have benefited from having the Executive Committee members participate directly in this JSR. Their insight and experience helped us to arrive at solutions that were realistic and beneficial to the widest group of community participants.”

The members of the two JCP Executive Committees formed the Expert Group(EG) for this specification. Over the course of eight months they worked closely with the rest of the community to define a process JSR that will make the JCP one of the most rewarding collaborations and innovation ecosystems for developers.

Doug Lea, professor at State University of New York Oswego comments, “I’m pleased that open processes like those used already in a few JSRs will now become the expected way for JCP specification efforts to proceed. We found in JSR 166 that opening up channels for involvement by interested developers improves specifications, tests, and implementations. It’s also more productive and pleasant. Expert groups can accept good ideas and critiques early enough to make a difference, and can produce final deliverables with more confidence that they will be widely accepted and used.”

“The changes found in JCP 2.6 represent another step forward by the Executive Committee and PMO to move the JCP to a more open and collaborative specification process,” said Geir Magnusson Jr, VP of Java Community Process, Apache Software Foundation. “This JSR builds on the progress of JCP 2.5 in two ways. The first is the encouragement of transparency in the activities of expert groups, a proven aspect of successful collaborative development. The second is a process change to provide a preliminary version of the spec to the developer community early in the specification process. Through this, the community can help shape the specification with early feedback, and the expert groups can act on this feedback before too much work is complete. We think that these two changes alone will help the Java developer community build better and more widely adopted technology specifications.”

“JPC 2.6, the next step in the continuing evolution of the Java Community Process, further opens JCP processes and reaches out to Java developers beyond current JCP members,” said Don Deutsch, vice president of standards, strategy and architecture at Oracle Corporation. “JCP 2.6 strengthens the link between Java platform development and the international Java developer community.”

“We have built the BlackBerry wireless platform on open industry standards like Java technology and are pleased that the JCP is continuing to evolve its standards definition process,” said David Yach, Vice President, Software at Research In Motion (RIM). “JCP 2.6 is helping to fuel the proliferation of Java technology and create an even more robust process by encouraging developers to become involved early on.”

“Harnessing innovation is essential to Symbian and other companies in the dynamic mobile phone market: JCP 2.6 will help the creation and delivery of innovative Java technology to this market,” said Jonathan Allin, Product Manager for Java, Symbian. “The more open access provided by JCP 2.6 will make it simpler for Java expert groups to utilize the talent of the smaller companies and individuals who fuel the growth of the wireless Java market, and will make it simpler for the expert groups to interwork with other organizations who provide complementary standards. In turn, earlier visibility of business terms and specifications will enable implementers to better plan the introduction of new JSRs. This latest release of the Java Community Process is an important step towards a truly inclusive community that will further the development and deployment of Java technology.”

For a complete listing of the JSR 215 EG members please visit

About the Java Community Process

Since its introduction in 1998 as the open, inclusive process to develop and revise Java technology specifications, reference implementations, and technology compatibility kits, the Java Community Process program has fostered the evolution of the Java platform in cooperation with the international Java developer community. The JCP has over 700 company and individual participants; more than 200 Java technology specifications are in development in the JCP program, of which 46 percent are in final stages. For more information on the JCP program, please visit