ReleaseStatus

Differences between revisions 1 and 568 (spanning 567 versions)
⇤ ← Revision 1 as of 2009-01-30 10:49:19 →
Size: 3068
Editor: p579DEA1E
Comment: status for 2009-01-30 meeting
← Revision 568 as of 2012-06-01 09:13:12 → ⇥
Size: 2372
Editor: seb128
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Line 4: Line 3:
== Specs ==
Most are approved and their implementation underway; exceptions:
 * kubuntu-jaunty-kde-packaging [drafting]: Waiting for KDE community decision about default IRC client
 * jaunty-desktop-network-changing [drafting]: This is mainly an umbrella for a list of bugs; Alexander filed all bugs and will summarize them in the blueprint, then it will be approved; many issues are already fixed in Jaunty		 == What was done engineering wise? ==
 * Specs writing is done
 * Continued on SRUs for precise
 * Good progresses on the third party drivers installation spec
 * New firefox (13) and thunderbird are ready for the coming release
 * Got firefox to build with the quantal toolchain
 * Libreoffice 3.5.4 SRU is ready for upload
 * Work on xorg for lts point release updates continued
 * compiz got refactored to be only one source rather than five, the packaging got updated and the new version is finally building
Line 9: Line 13:
== RC Bugs ==
 * https://launchpad.net/bugs/321311: screensaver won't unlock: Seb suspects an IM issue, will follow up in the bug; for now, this doesn't really deserve "critical" IMHO
 * https://launchpad.net/bugs/308397: ubufox breaks useragent stats: not really important, since we are being counted; "wontfix"ed stable task, taken off the list of alpha-4 blockers, and fixed in bzr already
 * https://launchpad.net/bugs/312536: nss shouldn't honor MD5 hash signatures -> waiting for upstream fix, security update issue, not really a release blocker, won't land in time for a4
 * https://launchpad.net/bugs/310999: nss shouldn't honor comodo CA? -> still waiting on upstream decision, security update issue, not really a release blocker, won't land in time for a4
 * known X regressions:
  * https://launchpad.net/bugs/264462: Bryce wrote debugging recipe into the wiki, waiting for reporter to provide debugging info
  * https://launchpad.net/bugs/304871: was believed fixed with dri2, but apparently not so; debugging going on (needs cofirmation that they were actually using dri2 in last test)
  * https://launchpad.net/bugs/308410: Blocked waiting on nVidia's driver release to match new X ABI (closed-source drivers); jockey doesn't currently offer them, for the time being
  * https://launchpad.net/bugs/312677: confirmed fixed
 * https://launchpad.net/bugs/287470: nvidia-graphics-drivers-173 upgrade failures, fixed in intrepid-updates
 * https://launchpad.net/bugs/284408: fglrx counterpart to 287470, blocked on AMD to provide a build against current X server; disabled in Jockey for now; ati should work for almost all users now, though
 * https://launchpad.net/bugs/309482: OEM mode failing for Kubuntu: still untriaged; pinged Riddell, he'll look at it
 * https://launchpad.net/bugs/314263: seems this is fixed for calling as real user, but still an issue with calling through root->su/sudo (i. e. what apport does for system crashes); Martin provided reproducer in the upstream bug		 == What's about to land that might impact the other teams? ==
Line 24: Line 15:
== Planned Intrusive changes ==
 * GNOME 2.59.90 is due next week; if we don't have time to push it in, due to sprint and alpha-4 freeze, we'll skip that and upload the next microversion the week after
 * Martin plans to update our patches for langpack support for .desktop files to the improved patches in OpenSUSE; making them fully "active" will require rebuilds of all packages, thus doing that right before a GNOME point release is a great time; it does not cause major problems if the rebuilds don't happen quickly, though.		  * Nothing specific

=== Summary of bugs working on by team (reasonably reliable) ===

 * No specific list yet for quantal

=== Dependencies on other teams to make deliverables, blocking items, release wide concerns? ===

 * None

== Blueprints ==

https://blueprints.launchpad.net/ubuntu/precise/+specs?searchtext=desktop-q-

Burndown and spec completion levels:

 * For alpha-1 milestone: http://status.ubuntu.com/ubuntu-quantal/canonical-desktop-team-quantal-alpha-1
 * Entire cycle: http://status.ubuntu.com/ubuntu-quantal/canonical-desktop-team.html

<<Anchor(rcbugs)>>

== Release targetted bugs being worked on/monitored ==

under investigation:
 * Bug:870297 ''[lightdm logins not being logged in wtmp]'': Still not reproducible. Dropped ubuntu-12.04 milestone, this is SRUable.

triaged/in progress:

 * Bug:932598 ''[Full hard drive causes xorg and lightdm to fail to load]'': Fixed mountall to create tmpfs /tmp on foll disk, as earlier Ubuntu releases used to do. lightdm still needs a fix.

Fix committed, but not uploaded yet:

 * Bug:872701 ''[Keyboard layout doesn't change in screensaver lock dialog]'': there is a fix upstream, should be included in the next gtk upload

Fixed since last report:
 * Bug:968845 ''[bcm5974 touchpad doesn't work after S3 on MacBookAir]'': should be fixed in quantal, SRU still be discussed (the fix is not perfect but fixes some issues)

<<Anchor(relnotes)>>

== Cumulative Desktop Release Notes ==

= Archive of previous weekly summaries =

=== 2012-05-25 ===

Done:

 * Catchup after UDS
 * Specs writing
 * Started quantal work, merges, some updates
 * Some SRUs for precise

This page keeps track of the current release status of the Desktop Team.

What was done engineering wise?

  • Specs writing is done
  • Continued on SRUs for precise
  • Good progresses on the third party drivers installation spec
  • New firefox (13) and thunderbird are ready for the coming release
  • Got firefox to build with the quantal toolchain
  • Libreoffice 3.5.4 SRU is ready for upload
  • Work on xorg for lts point release updates continued
  • compiz got refactored to be only one source rather than five, the packaging got updated and the new version is finally building

What's about to land that might impact the other teams?

  • Nothing specific

Summary of bugs working on by team (reasonably reliable)

  • No specific list yet for quantal

Dependencies on other teams to make deliverables, blocking items, release wide concerns?

  • None

Blueprints

https://blueprints.launchpad.net/ubuntu/precise/+specs?searchtext=desktop-q-

Burndown and spec completion levels:

Release targetted bugs being worked on/monitored

under investigation:

  • 870297 [lightdm logins not being logged in wtmp]: Still not reproducible. Dropped ubuntu-12.04 milestone, this is SRUable.

triaged/in progress:

  • 932598 [Full hard drive causes xorg and lightdm to fail to load]: Fixed mountall to create tmpfs /tmp on foll disk, as earlier Ubuntu releases used to do. lightdm still needs a fix.

Fix committed, but not uploaded yet:

  • 872701 [Keyboard layout doesn't change in screensaver lock dialog]: there is a fix upstream, should be included in the next gtk upload

Fixed since last report:

  • 968845 [bcm5974 touchpad doesn't work after S3 on MacBookAir]: should be fixed in quantal, SRU still be discussed (the fix is not perfect but fixes some issues)

Cumulative Desktop Release Notes

Archive of previous weekly summaries

2012-05-25

Done:

  • Catchup after UDS
  • Specs writing
  • Started quantal work, merges, some updates
  • Some SRUs for precise

CategoryDesktopTeam

DesktopTeam/ReleaseStatus (last edited 2012-07-12 20:12:57 by seb128)