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: 31

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

Presentation: Trustworthy Productivity: Securing AI-Accelerated Development

Sriram Madapusi Vasudevan discusses industry-converging patterns for securing autonomous AI agents in production. He explains the critical vulnerabilities hidden inside the ReAct loop across context, reasoning, and tool execution. He shares how to mitigate risks like memory poisoning and rogue tool execution using defense-in-depth strategies, LLM-as-a-judge critics, and MAESTRO threat modeling.

By Sriram Madapusi Vasudevan

Elastic Open-Sources Atlas Agent Memory Based on Cognitive Science

Elastic open-sourced Atlas, a system built on Elasticsearch that maintains three categories of memory for agents. Atlas integrates with agents via MCP and maintains per-user isolation of memories. When evaluated on question-answering capability, it scored 0.89 Recall@10.

By Anthony Alford

Microsoft Brings AI-Powered Vulnerability Remediation to Azure DevOps with Copilot Autofix

Microsoft has announced the limited public preview of Copilot Autofix for GitHub Advanced Security for Azure DevOps, extending AI-powered vulnerability remediation to teams using Azure Repos.

By Craig Risi

AWS Launches Lambda MicroVMs for Isolated Agent and User Code Execution

AWS launched Lambda MicroVMs, a new serverless compute primitive that runs each user session or AI agent in its own Firecracker virtual machine with hardware-level isolation, snapshot-based rapid launch, and state preservation for up to eight hours. Reddit community analysis found the minimum setup costs $3.03/day, roughly 9x Fargate spot pricing.

By Steef-Jan Wiggers

Article: Scaling Java-Based Real-Time Systems: The Hidden Tradeoffs of Event-Driven Design

Event-driven architecture promises scalability, but in Java-based real-time systems the tradeoffs only surface in production. Drawing on a Java/Kafka contact center platform handling 80k BHCC across 10k agents, this article details where the design breaks down—state management, partition limits, deduplication, JVM tuning, cascading consumer failures—and the Redis-backed patterns that fixed each.

By Sagar Deepak Joshi

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service