「DeveloperWiki:Extra パッケージの承認」の版間の差分
ナビゲーションに移動
検索に移動
(セクション見出しの訳出) |
|||
| 1行目: | 1行目: | ||
| − | [[ |
+ | [[カテゴリ:DeveloperWiki]] |
| + | [[en:DeveloperWiki:ExtraSignoffs]] |
||
| − | = Extra Signoffs = |
||
| + | = Extra パッケージの承認 = |
||
| − | === |
+ | === 手順 === |
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. |
||
| − | === |
+ | === 注意 === |
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. |
||
2020年5月7日 (木) 13:21時点における版
Extra パッケージの承認
手順
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.
注意
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.