Handling of Deviations from Standard Kernels

Registered by Stefan Bader on 2010-10-05

How do we handle drivers that are more recent than the rest of the kernel from a stable maintenance point of view?

Blueprint information

Status:
Complete
Approver:
Pete Graner
Priority:
Medium
Drafter:
Stefan Bader
Direction:
Approved
Assignee:
Stefan Bader
Definition:
Approved
Series goal:
Accepted for natty
Implementation:
Implemented
Milestone target:
milestone icon ubuntu-11.04
Started by
Stefan Bader on 2011-01-05
Completed by
Stefan Bader on 2011-01-05

Related branches

Sprints

Whiteboard

Status:
All actions completed.

Work Items for ubuntu-11.04:
[stefan-bader-canonical] document the why for each version deviant driver:DONE
[stefan-bader-canonical] stable tool to detect when a directory of patches are touching a deviant piece:DONE
[stefan-bader-canonical] document within the source tree a debian/deviant.versions type information:DONE
[stefan-bader-canonical] contact gregkh to see if we can use stable-review (NO):DONE
[stefan-bader-canonical] Create scripts to send out notifications for patches added and new releases of drm33:DONE

Topics to discuss:
* Better workflow for the 2.6.32.y-drm33.z upstream tree
* Always SRU drivers to upstream release versions?
* Actively track drivers or wait for submissions?
* Warning mechanism when modifying deviated drivers?

(?)

Work Items