Backports to v24 are now done, again with the exception of rc2_subset. This included the following packages:

• meas_base
• pipe_tasks
• drp_pipe
• obs_lsst
• ap_pipe
• pipelines_check
• 
  Changes in other packages were not backported for various reasons:
• ip_diffim: functionality that would have been modified was not yet present in v24
• drp_tasks: package did not exist in v24; new code from this branch was moved to pipe_tasks as part of the packport
• ap_verify: functionality that would have been modified was not yet present in v24
• analysis_tools: package did not exist in v24.

I'm not adding the backport-done label yet because I think we do care about rc2_subset, but for that I'm still blocked on the lack of release tags.

If Matthias Wittgen is not doing the tags you are going to have to add the v25 and v24 tags yourself based on the dates from the corresponding weekly that we branched the releases at.

Pushed these tags for rc2_subset
based}on weekly and release tags based on release tag dates.

 * [new tag]         24.0.0 -> 24.0.0

 * [new tag]         v24.0.0.rc1 -> v24.0.0.rc1

 * [new tag]         v25.0.0.rc1 -> v25.0.0.rc1

 * [new tag]         w.2022.28 -> w.2022.28

 * [new tag]         w.2022.48 -> w.2022.48

Thanks! I'll get the backports going on those shortly. I don't suppose we have a Jenkins job that can run the rc2_subset scripts on the release branch? (I'm guessing the answer is no, and get a custom lsstsw going at USDF on that assumption, but I'd love to be wrong.)

Backports for rc2_subset have been tested and merged; marking them as done.