Feedback regarding makinga mess of upgrade.

[lmf-git]

The chaos caused with this very over-complicated upgrade and all of the breaking changes have made me consider using somethingelse.

#2352

[nex3]

What specifically would you have preferred we do differently here? We announced the upcoming change more than three years ago, and we provided well over two and a half years between releasing the new API and starting to emit deprecation warnings. During this time, it was clearly documented on the Sass website and in JSDoc annotations that the legacy API was deprecated.

Before we started emitting deprecation warnings for the legacy API, we made sure there were fine-grained options to control deprecation messages in both the modern API and the legacy API. We even reached out to various frameworks we knew were still using the legacy API to warn them directly of the upcoming change.

Ultimately, the experience a user undergoes is primarily in the hands of the framework they interact with rather than the tools that framework uses. If we provide as much notice and documentation as we can of an upcoming change and the framework ignores it, there's very little we can do. If we provide detailed options to control warnings and the framework doesn't expose them to users, or doesn't explain to users how to access them, there's very little we can do. So I ask you: how did we "make a mess" of this upgrade? Or are you just frustrated because something changed and instead of choosing to help make the process better, you chose to lash out?

[nex3]

This is way out of bounds for the Sass code of conduct, and basic decency when interacting with someone who's providing you a product for free.