The analysis of the recent Amazon EBS outage has been posted on the AWS blog . I read it and was incredibly impressed with the detail, depth, clarity and competency shown. Of course, they need to impress the users with those things because they're asking us to trust them with our crown jewels.
Two Thursdays ago, I called for the community to vote for their top five issues, you responded with 186 votes, the results of which are captured in JIRA filter JSF_2_2_VOTED_ISSUES and in the following chart.
No, I'm not talking about implementing a Logo JSF RenderKit. I'm talking about a little image that can be used to represent the JSF specification on slides, web-sites, T-Shirts and such. JSF has been around for ten years now and still doesn't have a logo. As Dan Allen has repeatedly said, it's past time for that to change.
As mentioned earlier and elsewhere, JSF 2.2 is getting started right now. This blog entry is a call for serious, committed participation in the JCP Expert Group dedicated to delivering that specification.
I'm trying to provide transparency into Mojarra development practices and increase Mojarra code quality. To that end, this blog entry summarizes the current state of the Hudson jobs for Mojarra.
In an effort to promote my continuing belief that standards are for standardizing, and not innovating, I am announcing the start of the JSF 2.2 JSR effort with a blog entry mostly copied from the entry announcing the start of the previous iteration of the JSF JSR
In my last post, I announced that we had made a release candidate available for Mojarra 2.1.0.
While we work on the release notes and get ready to prepare a release bundle, I wanted to push this quick blog entry out as soon as I could. I just committed the integration of Mojarra 2.1.0 build 10 to the GlassFish 3.1 HEAD, it will be in the next promoted build of GlassFish.
Last week, I sent a code review request to the Mojarra dev list.