The IcedTea project provides a harness to build the source code from OpenJDK6 using Free Software build tools. It also includes the only Free Java plugin and Web Start implementation, and support for additional architectures over and above x86, x86_64 and SPARC via the Zero assembler port.

The IcedTea project provides a harness to build the source code from OpenJDK6 using Free Software build tools. It also includes the only Free Java plugin and Web Start implementation, and support for additional architectures over and above x86, x86_64 and SPARC via the Zero assembler port.

The Free Java devroom opened with an introduction from Tom Marble, followed by a ‘State of OpenJDK talk’ from Mark Reinhold and Joe Darcy. Mark reiterated the outline for JDK7 & 8 published on his blog. The general availability of OpenJDK 7 is planned for the 28th of July, 2011.

Oracle’s plans to continue with OpenJDK. Oracle employs around 20,000 Java developers, working on basically everything that is not the Oracle database. So their interest in Java is not altruistic, but based on rational self-interest. Mark outlined their priorities as:

Keep Java #1

Indirect Revenue

Direct Revenue

Decrease Cost

OpenJDK will continue to use GPLv2 with the Classpath exception as its license, though there is a possibility of moving up to GPLv3. The community bylaws were covered briefly, which sparked some discussion. Mark was careful to state that the current version is a draft; it is not immutable and will change. 4 weeks of discussion are planned, via the gb-discuss list, followed by a final vote to ratify the bylaws. Simon Phipps made some helpful contributions, including suggesting that laws should make sure that there is a transparent TCK license process and that the board be expanded to seven members, potentially allowing existing major contributors to OpenJDK, such as Red Hat, to be represented.

Joe Darcy then spoke on OpenJDK6. Going forward, Kelly O’Hair is to help with the OpenJDK6 release process. Security fixes will continue for OpenJDK6 until at least July 2012 (as 6 is already over three years old), and these will happen three times a year. This may eventually shift to the usual Oracle schedule of four times a year.

The good news is that OpenJDK7 will continue to be developed as it is now, without the issues that have plagued OpenJDK6 due to the separation between it and the proprietary release train. There will also be more transparency with release processes and development will continue to happen in the open.

Things do not look positive. The new rules set out a governing board (GB) dominated by assigned positions for Oracle and IBM employees (the latter having so far contributed little to OpenJDK). There are two elected positions, but the elections process described in the draft gives votes only to “OpenJDK Members”. These members are defined as those who have made “significant contributions” but with no description of how such significance will be decided. My guess is that most of these members, at least initially, will be Oracle employees as well, leading to the board being pretty much dominated by Oracle and IBM.

The rules also give overall power to the “OpenJDK lead” which is one of the two GB positions appointed by Oracle. They get to dictate the direction of the project.

There is some positive aspects, one of the main ones being the definition of an “OpenJDK participant” which finally allows trivial patches to be committed without the need for Oracle copyright assignment. However, the rules mainly codify the current status quo (which is far from ideal) in stone, entrenching Oracle as supreme overlords, and also giving rights to IBM, despite their lack of contribution to the project so far.

Even with a positive optimistic outlook, Simon Phipps ranks the rules as -3 on a scale of -10 to 10. An interim board has been established, throwing out the existing members and introducing three people who I’ve never seen contribute anything to OpenJDK.

The rules are still in draft, so there is room for change. But I’m not overly optimistic at this stage.

The public key I’ve had for the last three years or so was a 1024-bit DSA key with a SHA1 signature. With the discussion of the upcoming keysigning at FOSDEM, I decided it was about time for a new more secure key. Thus, I will be transitioning away from my old key to the following new key:

The old key will continue to be valid for some time, but i prefer all future correspondence to come to the new one. I would also like this new key to be re-integrated into the web of trust. The old key is signed with the new one and vice versa.

We are pleased to announce a new set of security releases, IcedTea6 1.7.8, IcedTea6 1.8.5 and IcedTea6 1.9.5.

This update contains the following security updates:

The IcedTea project provides a harness to build the source code from OpenJDK6 using Free Software build tools. It also includes the only Free Java plugin and Web Start implementation, and support for additional architectures over and above x86, x86_64 and SPARC via the Zero assembler port.