FFe for updating -ati/mesa/libdrm git snapshots until their individual releases
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libdrm (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
Karmic |
Fix Released
|
Wishlist
|
Unassigned | ||
mesa (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
Karmic |
Fix Released
|
Wishlist
|
Unassigned | ||
xserver-xorg-video-ati (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
Karmic |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: xserver-
[Request]
Standing FFe exceptions in Karmic for -ati until 6.13.0 (or 7.0.0?) release, libdrm until 2.4.13 (or 2.5.0?), and mesa until 7.6.0 in order to gain Kernel Mode-setting for ATI graphics hardware.
[Rationale]
KMS on -ati is a major goal for the Karmic release, yet KMS is not yet available in an official release. We have been carrying git snapshots of -ati, libdrm, and mesa in order to follow the current development, to enable testing and QA to proceed in parallel with upstream's work, so when a release does come we can integrate it with minimal worry.
[Testing]
In addition to validating updates on my own hardware, all git snapshot updates to Karmic are done only after the given snapshot has had some testing time in the xorg-edgers PPA repository. A number of users run this ppa and file bug reports when they spot problems, so this will help us avoid most critical issues. As well, by waiting a few days this lets us check the current git master to see if upstream put in important bug fixes.
Changed in xserver-xorg-video-ati (Ubuntu): | |
importance: | Undecided → Wishlist |
summary: |
- FFe for updating -ati/mesa/libdrm git snapshots until release + FFe for updating -ati/mesa/libdrm git snapshots until their individual + releases |
Changed in mesa (Ubuntu Karmic): | |
importance: | Undecided → Wishlist |
Changed in libdrm (Ubuntu Karmic): | |
importance: | Undecided → Wishlist |
Note that while we anticipate these three components will release prior to FinalFreeze (Oct 15th), none of these three projects publish roadmaps so it's difficult to project exactly when they'll release. Mesa usually publishes release-candidates for a few weeks prior to release, but has not begun doing this. The other two projects have not traditionally produced RCs.
Possible contingencies we're keeping and will begin evaluating as options starting at BetaFreeze for still-unreleased components are:
* Lock down on a particular git snapshot that pre-Beta testing has shown to be reasonably stable
* Revert back to prior stable release version
* Update the git snapshot during the week between Beta and FinalFreeze