Review the codebase and associated documentation, arbitrate last minute changes before going live:

• showstopper fixes
• make -devel packages noarch or not (golist issue 2)
• rpm macro & variable naming/bikeshedding if someone has better naming ideas
• use dynamic build dependencies or not. Probably yes if rpm PR593 is finished in time. Otherwise, three options:
  1. accept to wait some more for PR593 to be finished,
  2. fix the pm request mock plugin security so it is deployable in Koji, as discussed in FESCO issue 2004,
  3. accept to report dynamic build dependency to a later time. That means accepting to do another mass change later.
• and so on…