UME-MSG-Coordination
How to better coordinate UM&E and USG efforts?
Problem also involves syncing with distro and customer's requirements and schedules.
Idea is to do the next release in sync with Intrepid
USG needs drivers faster: customers see drivers posted by e.g. Intel and want them immediately
Drivers can either be updated blindly, or carefully checked; for USG updates, we would be ok with the former, for Ubuntu we need the later
It would make the work to update Ubuntu faster if we had the history/changelog information around the changes by Intel between releases and in shared components (e.g. libdrm).
Shouldn't update go via xorg instead of being dropped directly on our side? For example Intel could maintain a tree at freedesktop.org, or a public git tree on their site.
Ideally UM&E provides a qualified base release that Solutions group can layer onto.
Need to coordinate planning around the Hardy dot release
Coordinate schedule after RC for Intel SOW:
* USG team builds on RC and qualifies with customer additions and device
* identify issues to be resolved in conjunction with Hardy dot release update
Use weekly open IRC meeting to escalate USG issues and solutions
Provide more influence based on actual customer needs
Mention ongoing research / work during IRC meetings?
Discussion around Intel graphics
Changelog / history not made available; not clear which snapshot of e.g. libdrm Intel starts from
Need to test with latest drivers right way conflicts with process to validate the changes
Moblin work to track, connman, power, boot, etc
Reporting on the mobile list by the USG is really a helpful overview of the work in the team
USG to publish more changes directly to public trees, e.g. Launchpad bzr branches
MobileAndEmbedded/UME-MSG-Coordination (last edited 2008-08-06 16:28:04 by localhost)