Jul2008
3565
Comment:
|
3725
add agenda item
|
Deletions are marked like this. | Additions are marked like this. |
Line 61: | Line 61: |
* Discuss a new bug policy for updating bugs from release to release (proposal from Leann) | * Discuss a new bug policy for updating bugs from release to release (proposal from Leann) * Feedback regarding package status pages the qa team is prototyping: * Example page at: http://people.ubuntu.com/~ogasawara/pkg-stats/openoffice.org.html |
NOTE: This is just a place holder until the sprint takes place.
The July 2008 Sprint will take place at the Canonical Lexington Mass. office. Attendees:
- Ben Collins (Kernel Team)
- Pete Graner (Kernel Team)
- Tim Gardner (Kernel Team)
- Stefan Bader (Kernel Team)
- Leann Ogasawara (QA Team)
- Adilson Oliveira (FAE/SGE)
Agenda
Day 1 Monday 14 June 2008
AM Session
Discuss the role of a stable kernel engineer & job description (pgraner)
- Track CVEs and security issues
- Apply backports, develop fixes, work with Linux vendor community for resolution of security issues
Test & Validate Security Fixes
- Debian Packing hight desirable. (Can be taught)
- git understanding
- upstream kernel experience desired
- coordinate regression testing with the Ubuntu community.
- SRU development for Ubuntu stable releases
- driver backporting to stable releases
- work with QA to identify SRU candidates
- C programming essential
- upstream kernel or linux distro experience desired
- Daily Kernel Builds
- Decided on weekly. Daily builds fail to often.
- To be handled by the stable kernel position
- will need sync all modules i.e. lbm and friends
Discuss the policies regarding the current SRU practice for -updates => -security
- will merge at every Y release this will allow us to track the stable kernel sooner for a longer period.
- needs further discussion with rel-eng
- Review progress of fglrx and nvidia DKMS packaging
- Nvidia driver looks good
- ATI/fglrx ???
- Packaging Vanila Kernel Source
Reqested by QA & Support
- Needed as a reference point/check
- Kernel team noted that the vanilla kernel prob won't boot due to things like apparmor
- Would cause modules to not work in many cases i.e. lrm
- rtg's PPA is an alternative
Other option could be, every time we have a new rc release, rebase, build kernel.ubuntu.com, email to QA & Support. (2.6-27-rc1)
PM Session
Decide the fate of stable kABI [https://wiki.ubuntu.com/KernelTeam/Stable_kABI] (pgraner)1 hr.
Day 2 Tuesday 15 June 2008
AM Session
Overview of specs from UDS, defer, complete or mark as done. [https://wiki.ubuntu.com/KernelTeam/UDS/May2008]
- DKMS Packaging overview (by Ben?)
PM Session
Debian Packaging (Ben & Joint with server, by Kees?)
Day 3 Wednesday 16 June 2008
AM Session
- Discuss a new bug policy for updating bugs from release to release (proposal from Leann)
- Feedback regarding package status pages the qa team is prototyping:
Example page at: http://people.ubuntu.com/~ogasawara/pkg-stats/openoffice.org.html
Possibly use/link into http://www.kerneloops.org/ either from cmdline/apport, or LP?
PM Session
- Learn from kernel QA engineer (Leann) about best practices and processes for kernel bug triaging and isolating problems, especially some of its practices. Possible highlights, suspend/resume and sound. (requested by Adilson)
- Hardware Enablement Proposal Review (pgraner)1 hr.
Day 4
AM Session
- Kernel Packaging 101 (by Ben)
PM Session
- Learn how to track changes in kernel infrastructure, especially modifications to linux-ubuntu-modules (lum), linux-restricted-modules (lrm) and linux-backports-modules (requested by Adilson)
Day 5
- One on one time with team members
- Add hoc meeting/networking time
Sessions requested from kernel team
Put things here for OOB sessions with the kernel team or one of its members. Add your name for a list-of-interest.
KernelTeam/Sprints/Jul2008 (last edited 2008-08-06 16:17:40 by localhost)