.NET guidelines should clarify how source breaking changes can be made

[christothes]

Scenario:
A method with parameters that all have default values can be changed to having all required parameters when introducing a new overloasd that takes an options bag containing all the explicit parameters.

This is a source breaking change an not a binary break, which makes it acceptable.

[Tornhoof]

Please append to your guidelines that you put such source breaking changes into the release notes. I stumbled upon them during my update from 12.24.0 to 12.25.0

[ronniegeraghty]

Hey @christothes,
Can you give me more background here? Is this an ask to have better guidelines on what is considered a breaking change or better guidance on updating change logs when certain types of changes are made?

[christothes]

I think we should refine in the guidelines that we allow source breaking changes in certain scenarios, but never allow binary breaking changes. One example of a sourec breaking change is removing a method where all params are optional and replacing it with one where all params are mandatory (except for cancellation toke) and adding a method that takes an optional options bag containing the same params.