Raring
|
Size: 1885
Comment:
|
Size: 1974
Comment: weekly kernel team status - 2012-01-30
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| == Weekly Status 2012-01-23 == | == Weekly Status 2013-01-30 == |
| Line 11: | Line 11: |
| * 13.04 Month 3: http://status.ubuntu.com/ubuntu-raring/canonical-kernel-distro-team-ubuntu-13.04-month-4.html | * 13.04 Month 4: http://status.ubuntu.com/ubuntu-raring/canonical-kernel-distro-team-ubuntu-13.04-month-4.html |
| Line 18: | Line 18: |
| We have rebased our Raring kernel to the latest upstream v3.8-rc4 Linux kernel and uploaded. Please test and let us know your results. | We have rebased our Raring kernel to the latest upstream v3.8-rc5 Linux kernel and are intending to upload soon. We also saw the first pull request for arm multiplatform support [1] for TI omap3/4 and Freescale imx6. It is still undergoing some additional review. We also focused on debugging some power tests for QA as well as integrating and uploading some nexus7 kernel patches for config changes, fuel gage fixes, and reinstating a console quite level of 2. [1] https://lists.ubuntu.com/archives/kernel-team/2013-January/025186.html |
| Line 21: | Line 23: |
| We have also been working to isolate 2 regressions which were reported with the latest 3.5.0-22.34 Quantal kernel: * Bug:1103320 - Ubuntu 13.04 and 12.04.2: Login screen does not appear after installing OS on SL4545 G7 * The fix for this is cherry-picking upstream commit 51861d4e * Bug:1101666 - inotify fd leak * The fix for this will be to revert the problematic fsnotify patches. This will result in Bug:1096137 being re-opened and further investigation to discover a proper set of patches which do not introduce a regression. We intend to respin the Quantal kernel in order for these fixes to land in time for the 12.04.2 point release. |
See note about regarding arm multiplatform support. |
| Line 32: | Line 26: |
| Nothing at this time. | This isn't release critical by any means, but I'm curious if anyone on the release team happens to know how to go about resetting trend lines for our burn down charts? In particular, I'm interested in having my teams trend line reset: http://status.ubuntu.com/ubuntu-raring/canonical-kernel-distro-team.html |
Weekly Status 2013-01-30
Links to overall status, burn down charts, and work item tracking can be found at the following:
- Overall Status
- Burn Down Charts
- Work Item Tracking
What was done engineering wise?
We have rebased our Raring kernel to the latest upstream v3.8-rc5 Linux kernel and are intending to upload soon. We also saw the first pull request for arm multiplatform support [1] for TI omap3/4 and Freescale imx6. It is still undergoing some additional review. We also focused on debugging some power tests for QA as well as integrating and uploading some nexus7 kernel patches for config changes, fuel gage fixes, and reinstating a console quite level of 2.
[1] https://lists.ubuntu.com/archives/kernel-team/2013-January/025186.html
What's about to land that might impact the other teams and release as a whole?
See note about regarding arm multiplatform support.
Dependencies on other teams to make deliverables, blocking items, release wide concerns?
This isn't release critical by any means, but I'm curious if anyone on the release team happens to know how to go about resetting trend lines for our burn down charts? In particular, I'm interested in having my teams trend line reset:
http://status.ubuntu.com/ubuntu-raring/canonical-kernel-distro-team.html
Previous Meeting Summaries
KernelTeam/ReleaseStatus/Raring (last edited 2013-02-08 19:50:44 by c-67-171-179-115)