diff options
author | 2022-04-13 15:36:07 +0300 | |
---|---|---|
committer | 2022-04-16 10:27:55 +0300 | |
commit | 931d753612c9fdf8f54162deb1b0a4bf7f403833 (patch) | |
tree | 4bf6985cc886a4616d33b3b2c20f394687b7bbb2 | |
parent | ebuild-maintainer-quiz: adjust the GCC question (p3q12.) slightly (diff) | |
download | comrel-931d753612c9fdf8f54162deb1b0a4bf7f403833.tar.gz comrel-931d753612c9fdf8f54162deb1b0a4bf7f403833.tar.bz2 comrel-931d753612c9fdf8f54162deb1b0a4bf7f403833.zip |
ebuild-maintainer-quiz: deprecate repoman per council's decision
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
-rw-r--r-- | recruiters/quizzes/ebuild-maintainer-quiz.txt | 12 |
1 files changed, 4 insertions, 8 deletions
diff --git a/recruiters/quizzes/ebuild-maintainer-quiz.txt b/recruiters/quizzes/ebuild-maintainer-quiz.txt index b636913..54c151a 100644 --- a/recruiters/quizzes/ebuild-maintainer-quiz.txt +++ b/recruiters/quizzes/ebuild-maintainer-quiz.txt @@ -72,14 +72,10 @@ docs: devmanual docs: devmanual -3.a. What is repoman? When should it be used? How would you check for QA - problems with repoman? - -docs: devmanual, wiki - -3.b. A user submits a brand-new ebuild for a new package. What are - the proper steps (including repoman commands) to take to add - this ebuild to ::gentoo repository? What should be in the commit message? +3. A user submits a brand new ebuild for a new package. What are the proper + steps, including testing the contribution and checking for QA problems, to + add the ebuild to the ::gentoo repository? What should the commit's summary + look like, and how do you retain the authorship? docs: devmanual, wiki |