Follow-up from "DEP: Added deprecated warning for function transform_precessing_spins"

[bilby-bot]

In GitLab by @git.ligo:gregory.ashton on Feb 23, 2024, 15:57

The following discussion from !1329 should be addressed:

• [ ] @git.ligo:aditya.vijaykumar started a discussion:

  I'd recommend adding creating an issue to deprecate this with an expected timeline, just for documentation purposes.

[bilby-bot]

In GitLab by @git.ligo:colm.talbot on Feb 23, 2024, 16:17

I think there's a wider discussion to be had around this of setting up a procedure for deprecation and removal. As a toy example:

• mark the function/functionality to be removed with a DeprecationWarning, e.g., here.
• We should have a more specific template, maybe "... is deprecated as of vX.Y.Z and will be removed in vA.B" with vX.Y.Z the next planned release, and vA.B the next major/minor release with at least some amount of lag time.
• Removals explicitly only in major/minor releases.

This may be overkill, but I think it will allow us to remove some long-standing functionality that really hasn't been maintained or is causing bloat.