From a48ec3b99aff4dc19743dfa5f7f3da500c77d80f Mon Sep 17 00:00:00 2001 From: Ralph Bean Date: Aug 07 2017 15:34:21 +0000 Subject: Add a new package process SOP. Just some instructions for running the new client tools. Signed-off-by: Ralph Bean --- diff --git a/docs/source/sop.rst b/docs/source/sop.rst index 4cfdbc4..055bc60 100644 --- a/docs/source/sop.rst +++ b/docs/source/sop.rst @@ -64,6 +64,7 @@ Standard Operating Procedures sop_package_blocking sop_package_unblocking sop_pdc + sop_process_dist_git_requests sop_promoting_container_content sop_signing_builds sop_pushing_updates diff --git a/docs/source/sop_process_dist_git_requests.rst b/docs/source/sop_process_dist_git_requests.rst new file mode 100644 index 0000000..d350f83 --- /dev/null +++ b/docs/source/sop_process_dist_git_requests.rst @@ -0,0 +1,32 @@ +.. SPDX-License-Identifier: CC-BY-SA-3.0 + +================================= +Process dist-git-requests tickets +================================= + +Description +=========== + +When a packager wants a new package added to Fedora or a new dist-git branch +blessed, they need to go through the new package process and, once their +package review is approved, they use the `fedrepo-req` cli tool to file a +ticket in the `dist-git-requests queue `_. + +Periodically, (daily?) release engineering will need to review and process this queue using the `fedrepo-req-admin` tool. + +Setup +===== + +A release engineering will need to have several values set locally as well as +sufficient permissions in a number of server-side systems. + +#. A pagure.io token. See the fedrepo-req README for instructions on where to get this. +#. src.fedoraproject.org token generated by `pagure-admin`. Ask @pingou how to get one. +#. pdc token. See the PDC SOP for getting one of these. + +Action +====== + +#. Run `fedrepo-req-admin list` to list all open requests. +#. Run `fedrepo-req-admin process N` to process a particular ticket. +#. Run `fedrepo-req-admin processall` to iterate over all the tickets.