Purpose

The purpose of this page is to demonstrate that foo meets the architecture recertification criteria.

If some of these requirements are irrelevant or implausible for the port, please add a waiver request indicating why and how this isn't a problem for the arch in bold.

Availability

The architecture is publicly available without NDAs via:

  1. some vendor

  2. some other vendor

Developer machines

The following machines are available to developers:

  1. foo.debian.org - maintained by ..., connectivity via two tin cans and some string.

Port maintainers

The Debian port is maintained by the following developers, who actively work on architecture specific issues:

  1. ...
  2. ...
  3. ...
  4. ...
  5. ...

Users

The port is being actively used at the following sites:

  1. foo: xx machines, yy users, personal workstations
  2. bar: 1 machine, yyy users, development server
  3. ...

Popcon indicates zz users of the architecture as at 2005/xx/yy.

Installer

The installer is being maintained by ... and it's currently working effectively. Successful installation reports are available at: ...

Upstream support

Upstream support is provided by:

Archive coverage and Autobuilder support

Archive cleanliness

The port builds from unmodified Debian source.

Autobuilders

The following machines run buildds for the port:

Vetoes

The security team have noted the following problems in supporting the architecture:

The Debian admin team have noted the following problems in supporting the architecture:

The stable release team have noted the following problems in supporting the architecture:

The release team have noted the following problems in supporting the architecture:


CategoryLennyReleaseRecertification