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

Ny-a: /* Extra パッケージの承認 */ style: fix level 1 heading, extra blank line

2020-05-07T04:23:05Z

Extra パッケージの承認: style: fix level 1 heading, extra blank line

← 古い版		2020年5月7日 (木) 13:23時点における版
1行目:		1行目:
	[[カテゴリ:DeveloperWiki]]		[[カテゴリ:DeveloperWiki]]
	[[en:DeveloperWiki:ExtraSignoffs]]		[[en:DeveloperWiki:ExtraSignoffs]]
	= Extra パッケージの承認 =		== Extra パッケージの承認 ==


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

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

2020-05-07T04:22:09Z

注意: 訳出

← 古い版		2020年5月7日 (木) 13:22時点における版
17行目:		17行目:

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

	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-07T04:21:51Z

手順: 訳出

← 古い版		2020年5月7日 (木) 13:21時点における版
5行目:		5行目:

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

			手順は単純です。
	* If you need to test a package from the [extra] repository, you can add it to [testing]

	* When a [extra] package is placed in [testing] an email '''SHOULD''' be sent to the arch-dev-public mailing list with the subject "[signoff] [extra] foobar-1.0-1", where ''foobar-1.0-1'' is the package name and version.
			* [extra] リポジトリのパッケージのテストが必要であれば、[testing] に追加することができます。
	* In the email the maintainer has to say the reasons why that package went to [testing]
			* [extra] パッケージが [testing] に置かれたとき、arch-dev-public メーリングリストに "[signoff] [extra] foobar-1.0-1" という件名 (''foobar-1.0-1'' はパッケージの名前とバージョン) でメールを送る '''必要があります'''。
	* All developers are encouraged to test this package.
			* メールの中でメンテナはパッケージを [testing] に追加した理由を書く必要があります。
	* 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 [extra].
			* パッケージがうまく機能したら、メンテナにパッケージが機能したことと、どのアーキテクチャかを返信で伝える '''必要があります'''。
	* 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.
			* パッケージが全てのアーキテクチャで2つの承認を受け取ったとき、パッケージは [testing] から [extra] に移動できます。
			* メンテナは自由にパッケージを [testing] に残してより多くのテストや承認を受けることができますが、メールの中でこの意図を伝える必要があります。

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

Ny-a: セクション見出しの訳出

2020-05-07T04:21:16Z

セクション見出しの訳出

← 古い版		2020年5月7日 (木) 13:21時点における版
1行目:		1行目:
	[[~~Category~~:DeveloperWiki]]		[[カテゴリ:DeveloperWiki]]
			[[en:DeveloperWiki:ExtraSignoffs]]
	= Extra Signoffs =
			= Extra パッケージの承認 =


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

14行目:		15行目:
	* 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.		* 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.		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:ExtraSignoffs の版 600460 に同期

2020-05-07T04:19:23Z

en:DeveloperWiki:ExtraSignoffs の版 600460 に同期

新規ページ

[[Category:DeveloperWiki]]
= Extra Signoffs =

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

* If you need to test a package from the [extra] repository, you can add it to [testing]
* When a [extra] package is placed in [testing] an email '''SHOULD''' be sent to the arch-dev-public mailing list with the subject "[signoff] [extra] foobar-1.0-1", where ''foobar-1.0-1'' is the package name and version.
* In the email the maintainer has to say the reasons why that package went to [testing]
* 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 [extra].
* 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.