Hello!

Please find below the summary of the weekly report, which can be found in https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/WeeklyReport with more details and links.

The last meeting minutes: https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/Notes/2012-02-01

Please check also the Connect Graphics and Multimedia sessions as lined up through the blueprints: https://blueprints.launchpad.net/sprints/lcq1-12?searchtext=linaro-gfxmm

== Highlights == - 12.01 release completed, here are some statistics: + 3 out of 6 blueprints completed, + 2 Lava related blueprints moved to 12.02 (https://blueprints.launchpad.net/linaro-graphics-tests/+spec/lava-tests-run-... and https://blueprints.launchpad.net/linaro-graphics-dashboard/+spec/linaro-grap... both those blueprints are still in need of infrastructure) + the dma-buf + v4l2 as a user blueprint was put on hold since there is discussion ongoing related to the evolution of dma-buf

- Worked to resolve issues for the Nux/Compiz/Unity release, Unity with gles2.0 branch was approved and on its way to be merged

- Fixed display issue when playing two desktop scenes in a row, exposed by the canvas-reset branch functionality

== Issues == - Dashboard bugs: #881789 - timeout in image deployment and #904796 - provide staging/development lava server instances are a still there and pose a risk for our work with the LAVA dashboard for glmark2 tests

- The following issues need to be addressed for 12.02 release: + compiz issues (eg organize and prioritize the "refactoring" - chunking it down into manageable patches - of the compiz changes so we can move forward sanely) + upstream (e.g. dmabuf) review cycles + data publishing policy and what it means for our dashboard work

== Risks == - Even though there are actions now taken to deal with Unity/Nux/Compiz, it is possible that those packages are have issues which may require more time for the release - If the dashboard related bugs are not resolved during Connect it will be once again necessary to move those blueprints forward. This would be the 3rd milestone in a row where we move those blueprints, so we should work together with Validation team to make sure the bugs are resolved - Due to the current process of discussing the evolution of dma-buf with upstream (DRM and V4L2 communities) it is very probable to not have something ready for dma-buf for 12.02, we would then target 12.03 instead

Best regards,