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

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

30+ Updates per Second per Account: Uber Scales Ledger Processing with Batching

Uber introduced a high-throughput financial ledger processing system designed to handle hot account write contention at scale. Using 250ms batching, Redis coordination, and optimistic atomic updates, the system supports 30+ updates per second per account while preserving consistency and auditability, reducing multi-hour processing pipelines to minutes in its distributed accounting infrastructure.

By Leela Kumili

How a Culture of Data-Driven Conversations Can Support Platform Engineering

To provide SRE as a service, a team built a center of excellence, introducing Federated SREs and roles like production manager and technical tribe lead. They created a culture of data-driven conversations where SLOs and SLAs were democratised. Surviving growing cognitive load meant continuously simplifying architecture and embedding sovereignty and resilience into platform design decisions.

By Ben Linders

Presentation: Architecting a Centralized Platform for Data Deletion at Netflix

The speakers discuss the architectural challenges of executing safe data deletion across distributed datastores. Balancing durability, availability & correctness, they explain how to orchestrate multi-system deletion propagation without impacting live traffic. They share lessons on controlling tombstone accumulation, building continuous audit loops, and gaining trust with a centralized platform.

By Vidhya Arvind, Shawn Liu

Article: Architectural Change Cases: A Practical Tool for Evolutionary Architectures

Architectural change cases extend architecture decision record (ADR) thinking by evaluating how decisions may evolve over time. Change cases expose hidden assumptions and help teams estimate the reversibility and cost of change.

By Pierre Pureur, Kurt Bittner

AWS Replaces Fat-Tree Data Center Networks with Random Graph Theory, Cutting Routers by 69%

AWS disclosed that Resilient Network Graphs, a flat network architecture based on quasi-random graph theory, is now the default for most new data center builds. The design replaces fat-tree hierarchies with direct ToR-to-ToR mesh connections using passive optical ShuffleBoxes, cutting routers by 69%, boosting throughput by 33%, and reducing network power consumption by 40%.

By Steef-Jan Wiggers

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service