Differences between revisions 12 and 13
Revision 12 as of 2005-12-09 12:20:06
Size: 2970
Comment:
Revision 13 as of 2005-12-09 13:44:16
Size: 2933
Editor: ?FransPop
Comment: Fix typo, remove self as user
Deletions are marked like this. Additions are marked like this.
Line 19: Line 19:
     * Frans Pop (running Hercules)
* Stephen Frazier - State of Oklahoma Departmnet of Corrections
     * Stephen Frazier - State of Oklahoma Department of Corrections

The goal of this page is to collect the information necessary to demonstrate that the s390 architecture meets the [http://release.debian.org/etch_arch_criteria.html architecture recertification criteria for etch].

  • Availability: The architecture needs to be available for everybody, i.e. it must be available without ["NDAs"] and it must be possible to buy machines on the market.
  • Developers availability: The architecture must have a developer-available (i.e. debian.org) machine that contains the usual development chroots (at least stable, testing, unstable).
    • There is raptor.debian.org - ut raptor doesn't contain a testing chroot aba/2005-10-29
  • Users: The architecture needs to prove that developers and users are actually using it. Five Developers need to certify in that they're activly developing on this architecture, and it needs to be demonstrated that at least 50 users are using the platform.
    • Developers
      • Bastian Blank (Debian Developer)
      • Frank Kirschner (Debian Developer)
      • Frans Pop (Debian Developer - Installer stuff only)
    • Users
      • BfF (Bundesamt für Finanzen), 1500 Users
      • Stephen Frazier - State of Oklahoma Department of Corrections
  • Installer: The architecture must have a working, tested installer.
    • Debian-Installer exists for Sarge and continues to be developed for Etch.

(However, it does not currently support etch since parted doesn't support s390 in etch right now. Also, s390 is one of the few architectures not yet using partman.)

  • Porters and Upstream support: There is support by the porters and upstream. This is especially true for the toolchain and the kernel.
    • GCC, Linux, glibc, bintuils and gdb support is developed by IBM and integrated upstream.
  • Archive coverage: The architecture needs to have successfully compiled the current version of the overwhelming part of the archive, excluding architecture-specific packages.
  • Archive cleanliness: All binary packages need to be built from unmodified sources (i.e. from the source found in the ftp archive), and all binary packages need to be built by debian developers.
  • Autobuilder support: The architecture is able to keep up with unstable with not more than two buildds, has redundancy in the autobuilder network, keeps their autobuilders running for 24x7, has autobuilders acceptable for security support.
    • There are two autobuilder available, debian01.zseries.org and debian-31.osdl.marist.edu, one of them can easily keep up with unstable. Currently one builds oldstable, stable, stable-security and testing, both do unstable.
  • Veto powers: Security team, system administrators and release team must not veto inclusion.


CategoryEtchReleaseRecertification