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 Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1561002 Title: Ubuntu.Web QML component not providing stable versioned API Status in webbrowser-app package in Ubuntu: New Bug description: The webbrowser-app source package is what provides the Ubuntu.Web QML component. However, this component is not properly versioned in a stable way that aligns with the UITK versioning. As a result, apps are broken simply by newer versions of the package being included in updates. For example, if one has an application that uses Ubuntu.Web, but was still using the older Ubuntu.Components import, the newer version of Ubuntu.Web imports the newer Ubuntu.Components, which creates conflicts, and results in various aspects of the app being broken, in particular many elements have improper theme rendering. As a supported part of the SDK, this should never happen, and QML imports should be version stable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1561002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
