Can we chat about breaking changes in stable releases?

Fair criticism. Again, though, my point is less to debate the design and more to point out that the design on which you have settled has ramifications that I don’t currently feel are being respected.

Then why not immediately revert and go a different path? I see numerous pull requests to core projects fixing the fallout from this. There were numerous questions about it. But not until I whined was anything done about it. In my opinion, if it was truly unintentional, it should have been reverted as soon as you noticed breakage.

I appreciate that things are happening now, thank you both for that. However, I’d like to see some lessons learned and changes made, or this type of thing can easily happen again, further harming ROS 2’s reputation. Defining a tick/tock cycle and sticking to it is a satisfactory change.

1 Like