Please remember to update the README.md in scipipe_conda_env to describe how to generate these lockfiles. (Or remove that readme, and have the whole process documented somewhere central.)

I was worried about removing the python version option (because we might need to go to Py4 in the future), but Brian convinced me that this was only for the base miniconda environment and that it didn't affect our environment.

I was also questioning the conda clean commands, but they seem to be quite useful to minimize space utilization, so they can stay.

There are a couple of other trivial comments; the rest looks great.

Brian will use the same lock files that were generated a while back, as that is the environment we actually want to freeze. He will update the _packages file to correspond, even though we won't actually use it anymore. He will also add new versions of the lock, bleed, and packages files to the qserv branch for building that product.

Since the DMCCB has decided to implement this for the release to ensure reproducibility, this ticket should block the release.

If everything has been merge, can the status of this issue be changed to DONE, so I can start with the 20.0.0 release candidate 1?