We use 1 cycle of deprecation warnings, so old classes should still remain with a future warning that is raised at init saying that this class was deprecated in version 2.0.0 in favour of... and will be removed in version 2.1.0. User should use [new name of class] instead.
Add #TODO remove in version 2.1.0 on top of deprecated class.
tests should pass for both classes in version 2,0,0
We use 1 cycle of deprecation warnings, so old classes should still remain with a future warning that is raised at init saying that this class was deprecated in version 2.0.0 in favour of... and will be removed in version 2.1.0. User should use [new name of class] instead.
Add #TODO remove in version 2.1.0 on top of deprecated class.
tests should pass for both classes in version 2,0,0