Well, ideally without breaking the older version imports, yes. Sure, not anticipating changes is only part of the problem though.
Like the ABI requirements we have for C/C++ libraries, we also need to have similar checks and requirements for the APIs we provide as QML plug-ins. Unfortunately, I don't know exactly how to do that. A good start at least, would be to have some automated tests in various places that fail when these issues happen, so that we can at least catch them before all the apps in the store get broken and we don't misplace blame onto the apps for "using the UITK wrongly," when the components are what broke, and not the apps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561002 Title: Ubuntu.Web QML component not providing stable versioned API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1561002/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
