We may wish to consider what "all" the obs packages actually means. I assume at least cfht, decam and subaru, but not e.g. monocam.

I think Kian-Tat Lim was proposing we go maximal and see what breaks; with the understanding that if something in lsst_obs breaks we are allowed to remove the breaking package temporarily. obs_monocam is in lsst_py3 at the moment.

Yes, distributed "as-is" with no guarantee of merchantability or fitness for a particular purpose other than we managed to build it, and it passed its own tests on our platforms. Borrow some text from a shrink-wrap license for the README

obs_monocam cannot be broken by definition: it has no tests.

Does this then include all of the testdata packages?

The testdata packages will have to be excluded from the publish (they are optional) as we don't want eups distrib users downloading massive amounts of data (just like afwdata is excluded).

Ah! Ok, that makes sense. That method only works for eups distrib installs, not lsstsw, right?

lsstsw picks up optionals. I think that eups distrib server has an exclusion list containing afwdata but I'm not entirely sure. Or maybe that exclusion list is on the lsst-dev build system that does the rebuilds and publish.

Or maybe that exclusion list is on the lsst-dev build system that does the rebuilds and publish.

I believe this is lsst-dev.ncsa.illinois.edu:~lsstsw/etc/manifest.remap.

Who is on the hook for this work? It's blocking the 13.0 release so presumably we want to get it done ASAP.

John Swinbank I think the situation is that Frossie Economou will try to do it as part of the release packaging but she would be very happy if someone else volunteers the hour to do it.

Ok, then I'll set the team to SQuaRE.

There aren't repos.yaml entries for these obs_* packages so they are being excluded on the basis they have never been CI'd. obs_sst, obs_wiyn, obs_noao_mosaic

CI build of lsst_obs: https://ci.lsst.codes/job/stack-os-matrix/19357/

Note that new package does not show on issue as a branch: https://github.com/lsst/lsst_obs

Looks okay to me. Please remember to update the publishing system when you are done to make sure that we don't publish the testdata packages through eups distrib. I'll leave it in review state for Kian-Tat Lim.

@timj https://github.com/lsst/lsstsw/pull/153 should prevent eups distrib packages being created for the testdata* products.

Yes, I know, but you have to actually install those files in the right place on the right machine for that to be true.

Jenkins deploys lsstsw from master on each build. https://github.com/lsst-sqre/jenkins-dm-jobs/blob/master/jobs/run_rebuild.groovy#L25

Kian-Tat Lim Do you think you'll have time to give this a quick look over today? This is the last issue blocking the 13.0 release.

I've gone ahead and added lsst_obs to lsst_distrib as this ticket was marked as a blocker for the 13.0 release. We can roll it back if any problems crop up tomorrow.