Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add regret.policies.ElapsedTime #12

Open
Julian opened this issue Jul 12, 2020 · 0 comments
Open

Add regret.policies.ElapsedTime #12

Julian opened this issue Jul 12, 2020 · 0 comments

Comments

@Julian
Copy link
Owner

Julian commented Jul 12, 2020

This deprecation policy uses time-since-deprecation as the measure of when to remove an object (or permanently change it) once it has been deprecated.

Errors shown via #14 / #1 should be fired after the expected elapsed time has passed, and deprecations should require specifying the initial date.

Some concern may be paid towards the fact that typically deprecations will be performed some period of time before the version containing them is released. We can check what if anything projects that do deprecations in this way tend to do, which likely is either "ignore that fact if their releases are often enough", or add a fudge factor's worth of time onto the end, such that deprecations are removed after 13 months, say, instead of a year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant