dotnet
Document how we will update CLaSP in a highly compatible way
We will need to eventually make updates to CLaSP (implementation and/or interfaces). If we have a pattern to follow, we can know which sorts of changes are higher cost and which changes are lower cost. Let's make sure we have a pattern in place and documented in some location for it.
There does exist some documentation on how the VS LSP Client folks handle this: https://microsoft-my.sharepoint.com/:p:/p/maprospe/EUnLp6_EKv5FpEsDEFfrxVQBtivj8MszPgPhn2Qqyh4YfA?e=5MQA21.
Going to close this out. CLaSP is a source package owned by Roslyn, and being a source package its highly compatible - if it hurts when you upgrade, don't upgrade :)
