

There are probably edge cases and you might not know about them until you actually run into them by running a script or similar but then it is to late as people dont want things to break. There is 30 years of testing, and expected behavior, behind on what we have today.







Change => changing behavior etc. That is not a problem at all as long as it 100% compatible - which in this case is very hard to prove. The way to introduce change is therefore to say it is a new, different, standard. API version 2 or a new protocol, and let users migrate over to that by requesting the new version/protocol etc.
One difference is though that Ubuntu 26.10 is a new release(not LTS) so you would need to have a migration process anyway.