Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: afw, ap_association, cp_pipe, daf_butler, faro, ip_diffim, obs_base, pipe_base, pipe_tasks, skymap
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Team:Data Release Production
-
Urgent?:No
Description
Per RFC-945, code deprecated before v26 (rc1 is now expected to be w_2023_31) can now be marked as being scheduled for removal after v26 rather than after v27 (but note that we can't actually remove it from main until eight weeks have passed as well).
Attachments
Issue Links
- blocks
-
DM-36466 Do Release 26.0.0 of Science Pipelines
- In Progress
- relates to
-
DM-39841 Remove deprecated doPsfMatch fields
- To Do
-
DM-39914 Remove deprecated calib argument in Mag functor
- To Do
-
DM-38687 Remove code deprecated on DM-31924
- To Do
-
DM-40063 Remove deprecated ButlerQuantumContext
- To Do
-
DM-40065 Remove photodiode deprecations introduced in DM-38944
- To Do
-
DM-40067 Remove butler *Direct methods
- To Do
-
DM-40079 Remove Butler.datasetExists
- To Do
-
DM-40080 Remove public Butler.datastore property
- To Do
-
RFC-945 Clarify deprecation clock in the DM dev guide
- Implemented
- mentioned in
-
Page Loading...
This review should be entirely trivial, but I'm splitting it up as a way to make sure some tickets I created to track removal of some deprecated interfaces don't go unnoticed. There are only two kinds of commits: one that updates "removed after v27" deprecation warnings to say "removed after v26", and one that adds TODO comments with ticket numbers to deprecations for those removals. All of the removal tickets whose timelines have been adjusted are linked here, and I've updated their release blocking/blocked-by links as well.
Tim Jenness:
Christopher Waters:
Ian Sullivan: