touch-packages team mailing list archive

[Zsombor Egri <1461061@xxxxxxxxxxxxxxxxxx>]

This was a valid problem in the UI Toolkit in the previous versions - we
had the main component set 1.2, the ListItems 1.1, etc. From 15.10
onwards all its sub-modules, including themes will be aligned to 1.3
version, and the plan is that with the next LTS (16.04) we will open
2.0, which will not necessarily mean every LTS will bring  major release
update.

However. Bumping version with every release in modules which do not
bring new APIs are a bit of an overkill. For instance if Content Hub
brings a new API let's say in 1.4, and UI Toolkit doesn't bring anything
for 1.4, that would mean that we would need to duplicate theme files for
1.4 just because we need to rise the version of the toolkit, which is a
bit of an unnecessary work - remember, themes are loaded runtime and not
resolved through the QML type system, so qmldir tricks do not apply
there.


** Changed in: ubuntu-ui-toolkit (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1461061

Title:
  Normalizing import version across ubuntu components

Status in content-hub package in Ubuntu:
  New
Status in location-service package in Ubuntu:
  New
Status in media-hub package in Ubuntu:
  New
Status in u1db package in Ubuntu:
  New
Status in ubuntu-download-manager package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  Some components are still 1.0, other 1.3. It can be hard for the
  developer to understand exactly which version to import, what version
  is compatible or part of the same framework that the other one.

  The goal is to get a common agreements with all components we ship as
  part of the ubuntu sdk coming from canonical (from media-hub, content-
  hub to ubuntu components) to use the same API version for making
  easier developer's life experience.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1461061/+subscriptions