The TCK issue mentioned in our January report for 2014 still exists. Werner Punz summarized  and Leonardo Uribe discussed the impacts of this issue and the impacts are summarized as follows:
- reduces our marketability, since consumers are more likely to pick a fully-compatible open-source implementation over a partially-compatible open-source implementation.
- reduces our compatibility with other JSF implementations, which makes it more difficult for existing JSF consumers to switch over to MyFaces.
- reduces our compatibility with other JSF implementations, which makes it more difficult for third-party vendors to create libraries which work with all JSF implementations.
- reduces our an open-source JSF implementation certified as
"TCK-compliant" over a non-certified one.
- reduces our ability to be distributed as part of a J2EE stack, like such as TomEE and Geronimo, since their TCK compliance certification depends upon our TCK compliancecertification.
There are no new issues that require the board's attention at this time.