The JSF 2.0 project has reached the culmination of the XSLT contest and the scheduling exercises the JSF 2.0 Expert Group has been doing since August. I took the 88 issues in the query of issues we declared we’d try to do in the remainder of JSF 2.0, and used qoob’s XSLT sheet to produce an 88 page document, which I printed at Kinkos ($9.42 expense report forthcoming). I laid them all out in my living room, one deep, as shown in the “before” picture.

I walked around the issues and sorted them into 22 categories, see the “after” picture. The categories generally represent functional areas, with a few exceptions that can be considered cross-cutting concerns. The cross-cutting concerns include: javadocs, attributes and properties, class hierarchy, and value handling. The number of issues in each category is visually represented by the size of the pile. You can see that “Attributes and Properties” and “Validation and Conversion” have a lot of issues. I color coded the categories as well. Categories in red generally contain issues relating to the original charter of the JSR, and its Early Draft Review Goals. Categories in blue generally contain issues I think are important to improving the developer experience of using JSF to build solutions. Categories in yellow generally contain issues of importance to EG members and/or the companies they represent. Categories in black contain miscellaneous issues the EG and the public have determined are important to try to address in JSF 2.0.

Even with all this, no issue tracking system, no matter how awesome, is immune to GIGO. Therefore, it’s important that we use these 22 categories to ensure that the major tasks that remain to be done are captured. On the JSF IRC channel, we had a meeting yesterday where we tried to reduce the level of garbage going into the list and came up with this wiki page. This page, and the query of issues targeted for 2.0 will be our guide for the remaining seven weeks of time we have to define JSF 2.0.

To help us out, please, please, please review the Early Draft Review 2 draft of the spec and send comments to <jsr-314-comments@jcp.org>

Technorati Tags: edburns