=== What was done engineering wise? ===
* 12.04.1 ISO Testing and release. See jibel's report for full details:
https://wiki.ubuntu.com/QATeam/ReleaseReports/PrecisePoint1TestingReport
* Kicked off compiz / unity testing and unity multi-monitor bug triaging
* Shared results on some previous calls for testing:
* Webapps Testing - 16 people submitted 83 results and filed 18 bugs
* PulseaudioTesting - 12 people submitted 14 results and filed 0 bugs
* Kernel Testing - 38 people submitted 72 results and filed 22 bugs
* Evangelized new social media groups to promote ubuntu QA
* Shared definition and results of cadence testing; in short cadence
testing makes little sense in our current environment, but I would like
to see more work done to create an environment where it does makes sense :-)
=== What's about to land that might impact the other teams and
release as a whole? ===
* Community hardware database (looks like next month now)
* Excitedly awaiting the new ARM images with the 3d driver and unity
fixes :-)
=== Summary of bugs working on by team (reasonably reliable) ===
* N/S
=== Dependencies on other teams to make deliverables, blocking items,
release wide concerns? ===
* There have been some surprises in the past few weeks causing grief for
the testing community (nvidia/xorg changes, installer changes,
unity2d/unity3d, etc). I don't wish to discuss specifics on the changes
themselves, but rather how we can better communicate the work and
decisions that are made in advance so people can prepare and help work
through some of these difficult periods. As it stands, we leave the
community feeling caught off guard and upset about changes simply do to
the failure to communicate effectively.
Thanks,
Nicholas
--
Ubuntu-release mailing list
Ubuntu-release@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
