DeveloperWiki:Coreパッケージの承認 - 版の履歴

Ny-a: Ny-a がページ「DeveloperWiki:パッケージの承認」を「DeveloperWiki:Coreパッケージの承認」に移動しました: en:DeveloperWiki:ExtraSignoffs も存在するため

2020-05-04T04:24:37Z

Ny-a がページ「DeveloperWiki:パッケージの承認」を「DeveloperWiki:Coreパッケージの承認」に移動しました: en:DeveloperWiki:ExtraSignoffs も存在するため

← 古い版		2020年5月4日 (月) 13:24時点における版
(相違点なし)

Ny-a: style: remove extra blank line

2020-05-04T03:51:13Z

style: remove extra blank line

← 古い版		2020年5月4日 (月) 12:51時点における版
1行目:		1行目:
	[[カテゴリ:DeveloperWiki]]		[[カテゴリ:DeveloperWiki]]
	[[en:DeveloperWiki:CoreSignoffs]]		[[en:DeveloperWiki:CoreSignoffs]]

	== core パッケージの承認 ==		== core パッケージの承認 ==

Ny-a: /* 注意 */ 訳出

2020-05-04T03:50:33Z

注意: 訳出

← 古い版		2020年5月4日 (月) 12:50時点における版
20行目:		20行目:

	=== 注意 ===		=== 注意 ===

	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.
			メンテナ自身もパッケージを承認できます。メンテナは [testing] に置く前にパッケージをテストしているという仮定に基づいています。つまり、パッケージは元のメンテナがアップロード前に全てのアーキテクチャでテストしていれば、パッケージの承認は1つしか必要ありません。

Ny-a: /* 手順 */ 訳出

2020-05-04T03:50:16Z

手順: 訳出

← 古い版		2020年5月4日 (月) 12:50時点における版
9行目:		9行目:

	=== 手順 ===		=== 手順 ===
	The process is simple:

			手順は単純です。
	* All [core] packages '''MUST''' go to [testing] first.

	* Archweb automatically picks up the new package and allows developers and testers to signoff on [https://www.archlinux.org/packages/signoffs/ this page].
			* 全ての [core] パッケージははじめに [testing] に置かなければ '''なりません'''。
	* If a package works fine, the tester should signoff via archweb.
			* Archweb は自動的に新しいパッケージを見つけて、開発者とテスターが [https://www.archlinux.org/packages/signoffs/ このページ] でパッケージを承認できるようにします。
	* If it does not work, a bug report and/or email to the maintainer should be created/sent ASAP.
			* パッケージがうまく機能するなら、テスターは archweb からパッケージを承認する必要があります。
	* 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.
			* パッケージが全てのアーキテクチャについて2つ以上の承認を受けたら、[testing] から [core] に移動することができます。
			* メンテナはパッケージを [testing] に残して、より多くのテストや承認を受けることもできます。

	=== 注意 ===		=== 注意 ===

Ny-a: /* core パッケージの承認 */ 訳出

2020-05-04T03:49:54Z

core パッケージの承認: 訳出

← 古い版		2020年5月4日 (月) 12:49時点における版
4行目:		4行目:
	== core パッケージの承認 ==		== core パッケージの承認 ==

			このポリシーは [core] リポジトリ、つまり Arch Linux の core である部分が可能な限り常に機能することをより確実にすることを目的としています。パッケージは開発者・Trusted User・テスターによりテストされることができ、これらのグループは全員 archweb へのアクセス権限を持っています。
	This policy is intended to ensure the [core] repository, and thus the core of Arch Linux, is as functional as possible at all times. Packages can be tested by developers, Trusted Users and testers which all have access to archweb.

			パッケージのテストには単純な "起動するか" のテストから、もっと複雑なものまであります。通常、いくつかの単純な例 (例えば、"新しい linux カーネルでも起動するか" や "perl は私の持っている perl スクリプトを実行できるか" など) についてソフトウェアが機能し続けることを確認すれば十分です。主な目的は、とても激しく壊れてしまったパッケージを、多くのユーザーに影響が及ぶ前に見つけることです。
	Testing a package can range from a simple "does it start/run?" test to more complex ones. Normally checking if the software still works for some simple example (for example, "does the new linux kernel still boot" or "does perl still run some perl script I have?") is sufficient. The main goal is to catch very badly broken packages before they can hit a large number of users.

	=== 手順 ===		=== 手順 ===

Ny-a: fix heading style

2020-05-04T03:48:51Z

fix heading style

← 古い版		2020年5月4日 (月) 12:48時点における版
2行目:		2行目:
	[[en:DeveloperWiki:CoreSignoffs]]		[[en:DeveloperWiki:CoreSignoffs]]

	= core パッケージの承認 =		== core パッケージの承認 ==

	This policy is intended to ensure the [core] repository, and thus the core of Arch Linux, is as functional as possible at all times. Packages can be tested by developers, Trusted Users and testers which all have access to archweb.		This policy is intended to ensure the [core] repository, and thus the core of Arch Linux, is as functional as possible at all times. Packages can be tested by developers, Trusted Users and testers which all have access to archweb.

Ny-a: セクション見出しの訳出・言語間リンクの追加

2020-05-04T03:48:29Z

セクション見出しの訳出・言語間リンクの追加

← 古い版		2020年5月4日 (月) 12:48時点における版
1行目:		1行目:
	[[~~Category~~:DeveloperWiki]]		[[カテゴリ:DeveloperWiki]]
			[[en:DeveloperWiki:CoreSignoffs]]

			= core パッケージの承認 =
	= 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. Packages can be tested by developers, Trusted Users and testers which all have access to archweb.		This policy is intended to ensure the [core] repository, and thus the core of Arch Linux, is as functional as possible at all times. Packages can be tested by developers, Trusted Users and testers which all have access to archweb.
7行目:		8行目:
	Testing a package can range from a simple "does it start/run?" test to more complex ones. Normally checking if the software still works for some simple example (for example, "does the new linux kernel still boot" or "does perl still run some perl script I have?") is sufficient. The main goal is to catch very badly broken packages before they can hit a large number of users.		Testing a package can range from a simple "does it start/run?" test to more complex ones. Normally checking if the software still works for some simple example (for example, "does the new linux kernel still boot" or "does perl still run some perl script I have?") is sufficient. The main goal is to catch very badly broken packages before they can hit a large number of users.

	=== ~~Process~~ ===		=== 手順 ===
	The process is simple:		The process is simple:

17行目:		18行目:
	* A maintainer is free to leave a package in [testing] for further testing or signoffs.		* A maintainer is free to leave a package in [testing] for further testing or signoffs.

	=== ~~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.		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.

Ny-a: en:DeveloperWiki:Coresignoffs の版 600438 に同期

2020-05-04T03:46:16Z

en:DeveloperWiki:Coresignoffs の版 600438 に同期

新規ページ

[[Category:DeveloperWiki]]

= 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. Packages can be tested by developers, Trusted Users and testers which all have access to archweb.

Testing a package can range from a simple "does it start/run?" test to more complex ones. Normally checking if the software still works for some simple example (for example, "does the new linux kernel still boot" or "does perl still run some perl script I have?") is sufficient. The main goal is to catch very badly broken packages before they can hit a large number of users.

=== Process ===
The process is simple:

* All [core] packages '''MUST''' go to [testing] first.
* Archweb automatically picks up the new package and allows developers and testers to signoff on [https://www.archlinux.org/packages/signoffs/ this page].
* If a package works fine, the tester should signoff via archweb.
* If it does not work, a bug report and/or email to the maintainer should be created/sent ASAP.
* 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.

=== 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.