[Library] Definitely retire Rhino Mocks
Closed this issue · 2 comments
What change would you like to make to the tech radar?
I'd like to move Rhino.Mocks back to Retire but with better documentation on why 😄
We should retire Rhino.Mocks when we're trying to move corresponding libraries over to .NET Core. The reason is that Rhino.Mocks does not support .NET Core.
Why do you believe this is valuable to Redgate?
As part of our .NET Core work.
Where should this be on the tech radar?
Retire. With caveats.
If this should be in the Explore ring, who is committed to exploring it?
N/A
Standard caveat: I'm super onboard with retiring stuff, but trying to be critical.
I think the "caveats" you mention actually mean this is best left in Endure.
Endure - This is no longer how we do things. It is OK for this to be used in Product Development, but don't add more of it and migrate off it wherever possible.
Retire - Don't use this technology! If you are using it then you should be spending some time migrating away from this. [sic]
(emphasis added.)
Moving something to run on .Net Core will mean Rhino Mocks must be removed, enforcing the "migrate of fit wherever possible" part of Endure. I think we'd continue to Endure Rhino Mocks anywhere we don't target .Net Core.
If we're not actively planning to prioritise retiring something, then I'm not sure it should be in Retire.
I'm happy with that, let's close this down.