Documenting Release Engineering Scripts

[Rob Marshall]

As I work my way through updating all of our release engineering scripts for
use under Python3 I have been asking a lot of questions to fill in the gaps
in our documentation.

Today I filed a user story with sub-tasks for each script in Taiga to make
this process a little easier. The goal is to use this documentation
initiative
to better understand our processes and make it easier to both update the
scripts and onboard newcomers.

I just filed the user story this afternoon and filled in what I learned
about
block_retired.py while looking at it for python3 porting today.

My ask is for those who know about the scripts and their processes to help
fill in the following:

- link to the SOP document(s) that do or SHOULD reference the script
- information about when this script gets run
- information about WHERE the script should be run
- information about any other requirements for the script's environment
- challenges/changes that may not be obvious from just the code
- anything else important about the script not in the above

You can find the Taiga user story here:

https://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-t...

The board's login authentication is handled by FAS. It's been my experience
that in order to get membership you need to first sign into Taiga and then
you can be added to the actual project. For those who are not already added
to
this board I can add you upon request after your first sign-in.

Thanks in advance,

--Kellin