XRoadmapDapper

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2005-11-01 14:00:55 →
Size: 1610
Editor: 198_220_103_66-WIFI_HOTSPOTS
Comment: spec for X maintenance for dapper
← Revision 2 as of 2005-11-01 14:02:59 → ⇥
Size: 1610
Editor: 198_220_103_66-WIFI_HOTSPOTS
Comment: inability to type \m/
Deletions are marked like this. Additions are marked like this.
Line 43: Line 43:
 * Which input drivers to people still use? DanielStone thinks: not many.  * Which input drivers do people still use? DanielStone thinks: not many.

Summary

Plans for continuing maintenance of X packaging in Dapper, or, 'care and feeding of your modular tree'.

Rationale

The modular tree of X has just been introduced to Dapper. As Dapper is to be supportable for quite some time, and we're new to the modular-tree-maintenance game, we need to carefully manage X in Dapper.

Use cases

Scope

  • X protocol packages: x11proto-*-dev
  • X library packages: too many to enumerate
  • X servers: xorg-server, xserver-kdrive (universe)
  • Xorg DDX drivers: xserver-xorg-(driver|input)-*
  • Mesa libGL and DRI drivers: mesa

Design

Implementation

  • Continue updating from release tarballs when released through to the release of R7 in December. Future bugfix updates on a case-by-case basis.
  • Updates from CVS where appropriate and where stability won't be harmed.
  • Ubuntu patches to be committed upstream ASAP.
  • List of supported input drivers to be sanitised.
  • Unify Mesa packaging with Debian.
  • Ensure we don't do anything stupid with the X server/driver packages that would be a showstopper for Debian's adoption of same.

Code

Data preservation and migration

Outstanding issues

  • Which input drivers do people still use? DanielStone thinks: not many.

BoF agenda and discussion

XRoadmapDapper (last edited 2008-08-06 16:16:06 by localhost)