Hello everyone, Recently, there were a lot of discussions about the deprecation of various APIs for the upcoming 2.0 release. It appears there are two main motivations with opposing directions, causing these discussions to remain unsettled. On one hand, there's a desire to finally trim a wide range of legacy APIs, some lingering around since the beginning of the 1.x release line (as far back as 2016). On the other hand, there is a commitment to uphold our guarantees to the users, ensuring a smooth transition.
I believe we could reconcile these two motivations. My proposition is to designate the final release of the 1.x timeline as a Long-Term Support (LTS) release. By doing so, we would: 1. Enable more efficient cleanup and be liberated to introduce more breaking changes, paving the way for greater innovation in the 2.0 release. 2. Sustain a positive user experience by granting enough time for the changes introduced in 2.0 to stabilize, allowing users to confidently transition their production code to the new release. I look forward to hearing your thoughts on this proposal. Best Regards, Alex
