Revision as of 05:54, 12 February 2010

Contents

Core Signoffs

This policy is intended to ensure the [core] repository, and thus the core of Arch Linux, is as functional as possible at all times.

Process

The process is simple:

All [core] packages MUST go to [testing] first.

When a [core] package is placed in [testing] an email SHOULD be sent to the arch-dev-public mailing list with the subject "[signoff] foobar-1.0-1", where foobar-1.0-1 is the package name and version.

All developers are encouraged to test this package.

If a package works fine, a reply SHOULD be sent, telling the maintainer it worked, and on which architecture.

When a package receives 2 signoffs for each architecture, it can be moved from [testing] to [core].

A maintainer is free to leave a package in [testing] for further testing or signoffs, but should make this intention known in the signoff email.

Caveats

The maintainer himself *DOES* count as a signoff. We are working under the assumption that the maintainer did test the package before pushing it to [testing]. Thus, a package may only need one signoff if the original maintainer tested it on both architectures before uploading.

List of potential signees for low-usage core packages

This list is to improve the effectiveness of the signoffs by determining what packages can't get the required signoffs by the dev group. Please put your name (or nick) and the arch (i686, x86_64, both) along the low-usage packages you can test. I'm listing here all the core packages. The ones that I believe everyone use and can test (please fix if they are incorrect or missing) are marked by a 'EVERYONE' so you don't need to write your name beside them.