I'd prefer that something containing the string ci have at least one component that is actually used continuously (i.e. on every build). A package that is used solely at nightly cadence would naturally have nightly in the name. Merging multiple cadences into one package is acceptable, but I think that could lead to problems with dependencies on data packages.

Understood and agreed. lsst_ci will have at least one thing that is intended to be built with every build (the obs_chft and obs_decam packages with their testdata suites).

More details at DM-5370

I suggest that we see how the balance between data size, real-time CI, and night builds works out. It's possible that DM-5370 will result in both a lsst_ci and lsst_nightly package, but if data size doesn't become to annoying, I'd prefer the single lsst_ci package that just gets run in an expanded mode for the nightly build to reduce the chance of the code drifting between the packages.

Right now lsst_qa this is just a simple meta package that includes your requested dependencies.

This looks great.

My only minor suggestion is to say a bit more in the README.md about validation tests – I found it a bit confusing that only three validation_data package exist, but the package lists more cameras than that. The trick will be not saying things that need to be constantly updated.

Updated README to clarify 3 validation_data sets, plus data in obs_sdss, and obs_lsstSim would likely use generated simulated data.

Merged to master.