Jan. 21, 2021
10:44 a.m.
Currently, we wait until the first user complains, sometimes after a 3.x.0 final release, before starting to document how to port existing code. I agree that it should be done earlier. I suggest that developers who want to introduce an incompatible change think about how to port existing code, especially if it's possible to write code compatible with the old and the new behavior. It should be done while the incompatible change is designed. I also agree that we document how to port code in the change which introduce the deprecation, not when we introduce the incompatible change (ex: remove a function). I also suggest to communicate on future incompatible changes ;-) Victor