Details
-
Type:
RFC
-
Status: Implemented
-
Resolution: Done
-
Component/s: DM
-
Labels:None
-
Location:this issue page
Description
I don't think there's anything in any of these packages that is currently in use or planned to be in use in the future (functionality previously provided by these packages will be rewritten from the ground up).
My main goal here is to retire ap, which is a dependency of the others, so I can make modifications to afw::table (such as on DM-1766) without having to worry about breaking it. If we can find a way to drop ap without dropping the others, I'd be satisfied, but I don't currently know of any reason to keep the others around.
Note that the deadline for this RFC is early next week, and I'd like to stick to that, as I hope to merge DM-1766 soon, whether that means I have to include a patch to ap or not.
Attachments
Issue Links
- blocks
-
DM-1766 Remove in-memory support of old-version afw::table objects
- Done
- is triggering
-
DM-1674 Data ingest scripts cleanup
- Done
-
DM-2948 Remove explicit buildbot dependency on datarel
- Done
-
DM-2928 move old ingest scripts into and retire old packages
- Won't Fix
- relates to
-
DM-2772 datarel tests depend on EUPS
- Done
-
DM-2773 testing_endtoend tests depend on EUPS
- Done
-
RFC-275 Add daf_ingest to lsst_distrib
- Withdrawn
So, it sounds like I should:
Any objections to me doing this as a subtask issue of
DM-1674? I'm happy to do this much myself, to unblockDM-1766(and then leave the rest ofDM-1674to the DB team).