Here's an update from the Chair of the JCP and director of the JCP Program office: Patrick Curran

http://java.ulitzer.com/node/965152


JSR Watch: Here’s to Progress

And here’s to the next 10 years!
By Patrick Curran

May 15, 2009 03:00 PM EDT
Reads: 560

The end of the year is an opportunity to review the past year's activity, and to present this to our Executive Committee (EC) members, to our broader membership, and to the general public. So this month I will summarize our progress during the past year.

PMO Initiatives
First, in addition to the ongoing work of moving JSRs through the process (more on this later), the JCP engaged in a couple of new initiatives around transparency and agility.

I've addressed the transparency issue relatively recently in this column, so I won't say much more here except to remind you that we are now strongly encouraging all Expert Groups (EGs) to work in an open and transparent manner by adopting practices such as the use of public mailing lists and issue-tracking mechanisms. Of course, it would be hypocritical for us to encourage this behavior in EGs while continuing to hold Executive Committee (EC) meetings in private, so there too we are becoming more open. Starting in September 2008 the ECs agreed to make full minutes and meeting materials accessible to the general public rather than simply posting summaries that only JCP members could read. (We reserve the right to go into Private Session from time to time when sensitive matters are discussed, but we don't expect to do this very often.) If you want to see what we're up to, the meeting materials are accessible.

As for agility, when I reviewed 2007 activity this time last year it became apparent that the amount of time it takes Expert Groups to complete their work varies significantly. Some manage to finish in a little more than a year, while others take several years. Also, we know that there are some JSRs that are effectively stalled and really ought to be withdrawn. As a first step to encourage agility we decided to introduce a new category for JSRs that have made no progress for 18 months - these will be labeled as "Inactive" on jcp.org. The PMO will work with the Spec Leads of these JSRs to encourage them to pick up the pace. If it becomes clear that the JSR is unlikely to complete, we will encourage them to withdraw it. In addition, we plan to review all JSRs that reach completion, and others as appropriate, to identify and publicize the good (and bad) practices that affect the speed with which JSRs move through the process.


There's more! Read the rest in J2SE Town...

Views: 41

Comment

You need to be a member of Codetown to add comments!

Join Codetown

Happy 10th year, JCertif!

Notes

Welcome to Codetown!

Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.

When you create a profile for yourself you get a personal page automatically. That's where you can be creative and do your own thing. People who want to get to know you will click on your name or picture and…
Continue

Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.

Looking for Jobs or Staff?

Check out the Codetown Jobs group.

 

Enjoy the site? Support Codetown with your donation.



InfoQ Reading List

MCP C# SDK 2.0 Makes HTTP Stateless by Default and Adds Multi Round-Trip Requests

Microsoft announced version 2.0 of the official MCP C# SDK, which implements the 2026-07-28 revision of the Model Context Protocol with stateless HTTP servers by default, standardised routing headers and Multi Round-Trip Requests. Releases 2.1 to 2.3 have since added hybrid session serving, a subscriptions/listen handler and a series of discovery, OAuth and shutdown fixes.

By Edin Kapić

PHP Patches Two Critical RCE Flaws That Were Already Under Attack

PHP released 8.5.12, 8.4.27, 8.3.36, and 8.2.35 to fix two critical vulnerabilities allowing unauthenticated remote code execution. Amazon recorded an exploitation attempt four days before the patches shipped, and operators spent the day working out whether they ran PHP, where to get the package, and how to tell it had landed.

By Steef-Jan Wiggers

PyTorch Conference 2026: Google and Meta Open-Source TorchTPU for Native PyTorch on TPUs

Google and Meta open-sourced TorchTPU, a native PyTorch backend for Google's TPUs, at PyTorch Conference North America 2026, and Meta said it plans to move larger LLM workloads onto TPUs with it. AWS released TorchNeuron for Trainium the same week, while developers questioned TPU availability and where vendor lock-in now sits.

By Andrew Hoblitzell

Google ML Drift Accelerates On-Device AI Inference Across Diverse GPUs

Google has released ML Drift, an open-source, cross-platform GPU compute engine designed for on-device AI and machine learning inference. Licensed under Apache 2.0, it abstracts the complexities of different GPU hardware and low-level APIs, supporting OpenGL ES, OpenCL, Metal, and WebGPU.

By Sergio De Simone

PingCAP Breach Exposes Customer Records and Source Code

PingCAP recently confirmed unauthorized access to its internal systems and the theft of source code and customer-related data. The attacker, cyber extortion group FulcrumSec, claimed to have stolen 10.6 TB of data, including TiDB Cloud control-plane records, customer SQL statements, API keys, connection logs, billing information, internal documents, and 413 private source-code repositories.

By Renato Losio

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service