2011-11-29

Differences between revisions 3 and 4
Revision 3 as of 2011-11-29 11:39:40
Size: 1396
Editor: seb128
Comment:
Revision 4 as of 2011-11-29 14:35:06
Size: 3317
Editor: didrocks
Comment:
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
 * More more more oneconf tests (logical tests, syncing tests) with changes in the infra. Still some tests to write and oneconf will be fully tested! (didrocks)
Line 20: Line 21:

 * Still some QA work to get automated tests and coordination in unity, unity-2d and all related components.
 * Compiz got some work on the testing infrastructure side, closer than what we were to get tests!
 * Some work on the infrastructure side as well. We now have automatic landing of unity components branches (detailed email at https://lists.ubuntu.com/archives/ubuntu-desktop/2011-November/003492.html). The resulting packages are pushed to https://launchpad.net/~unity-team/+archive/staging
  * After some last minute work on some components to have "make check" passing on headless and chroot builder.
  * Components that works: bamf, bamf-qt, dee, dee-qt, libunity, libunity-misc, nux, unity-2d, unity-asset-pool, unity-lens-applications, unity-lens-files, unity-lens-music.
  * Component still needing some work to have "make check" passing: unity
  * tarmac/jenkins Build result can be seen there: https://jenkins.qa.ubuntu.com/view/Precise%20Unity%20Merger/ (new projects appear as soon as there is a new approved merge request to one)
  * The infrastructure is generic enough to be able to deploy it for the desktop team where we are upstream as well if the need is there.
 * Worked with evan to define where the autopilot tests will be run. It will be on post-merge. Will need some hacking on tarmac to put it in "lock mode" in case autopilot found a regression (and then unlocking it).
 * Lot of discussion with various dx team members to ack on the plan of action.
 * All tarmac branches have been pushed upstream and waiting on merge review.
 * Wrote 107 manual tests (https://wiki.ubuntu.com/UnityTests), fully functionnaly covering panel, launcher, dash and alt + tab. Some window management interaction is covered as well.

Weekly Summary

  • Switched precise over to Rhythmbox, dropped banshee/gbrainy/totem/Mono from CDs. (pitti)
  • New oneiric language packs hit -proposed, please test. (pitti)
  • More packages got DEP-8 autopkgtest control files now. We now have apport, jockey, upower, postgresql-common; udisks is committed but not uploaded yet (pitti)
  • Update our desktop packages (polkit, accountsservice, etc.) for the adminsudo group migration. This is now the new preferred "administrator" group, but admin should still be recognized for backwards compatibility (for eternity). (pitti)

  • GTK 3 packages are now multi-arched, so you can start multiarching plugins and dependencies. (pitti)
  • Landed client-side crash duplicate checking in Apport, which makes reporting crashes a lot more enjoyable. (pitti)

  • Continued on desktop merges (seb128), there is enough work for several people though so extra hands would be welcome
  • Continued reviewing desktop bugs to nominate for the lts (seb128)
  • More more more oneconf tests (logical tests, syncing tests) with changes in the infra. Still some tests to write and oneconf will be fully tested! (didrocks)

Agenda

  • Insert things to discuss at meeting here..

Partner update

Unity

  • Still some QA work to get automated tests and coordination in unity, unity-2d and all related components.
  • Compiz got some work on the testing infrastructure side, closer than what we were to get tests!
  • Some work on the infrastructure side as well. We now have automatic landing of unity components branches (detailed email at https://lists.ubuntu.com/archives/ubuntu-desktop/2011-November/003492.html). The resulting packages are pushed to https://launchpad.net/~unity-team/+archive/staging

    • After some last minute work on some components to have "make check" passing on headless and chroot builder.
    • Components that works: bamf, bamf-qt, dee, dee-qt, libunity, libunity-misc, nux, unity-2d, unity-asset-pool, unity-lens-applications, unity-lens-files, unity-lens-music.
    • Component still needing some work to have "make check" passing: unity
    • tarmac/jenkins Build result can be seen there: https://jenkins.qa.ubuntu.com/view/Precise%20Unity%20Merger/ (new projects appear as soon as there is a new approved merge request to one)

    • The infrastructure is generic enough to be able to deploy it for the desktop team where we are upstream as well if the need is there.
  • Worked with evan to define where the autopilot tests will be run. It will be on post-merge. Will need some hacking on tarmac to put it in "lock mode" in case autopilot found a regression (and then unlocking it).
  • Lot of discussion with various dx team members to ack on the plan of action.
  • All tarmac branches have been pushed upstream and waiting on merge review.
  • Wrote 107 manual tests (https://wiki.ubuntu.com/UnityTests), fully functionnaly covering panel, launcher, dash and alt + tab. Some window management interaction is covered as well.

Software Center

Kubuntu

X.org

IRC log Western edition

IRC log Eastern edition

DesktopTeam/Meeting/2011-11-29 (last edited 2011-11-29 23:33:36 by bryce)