JCP.next.3: the next revision of the Java Community Process
Patrick Curran, the chair of the Java Community Process (JCP), has summarised current efforts to revise the body that standardises the Java programming language. Previously announced were JCP.next.1 and JCP.next.2 which followed it in January 2012 – both have already been given JSRs (Java Specification Requests). There is now also a JSR for a third initiative called JCP.next.3.
The three JSRs aim at creating a higher level of transparency for the community process, and at reducing the hurdles for participation in expert groups and committees. They also intend to increase process agility and merge the executive committees. The aim is to refresh processes and structures last updated in 2002.
JCP.next.1 was approved in JSR 348 ("Towards a new version of the Java Community Process") in October 2011. It contains a range of simple but important changes that are designed to increase process transparency and promote JCP participation. JCP.next.2 is currently being developed within JSR 355 ("JCP Executive Merge") and scheduled to be completed later this year. It deals with merging the currently separate executive committees for Java ME (Java Micro Edition) and for Java SE (Java Standard Edition) and Java EE (Java Enterprise Edition).
Among other things, the still emerging JSR 358 ("A major revision of the Java Community Process") – JCP.next.3 – contains a revised Java Specification Participation Agreement (JSPA) describing the rules that govern how JCP members can participate in the development of a JSR; it also includes major changes that were previously deferred from JSR 348. "We expect to spend a considerable amount of time working on it – at least a year, and probably more", said Curran. The process will be operated transparently with a public mailing list for observers, issues tracked on a public tracker and all documents made available in a document archive.