Normalizing import version across ubuntu components
Bug #1461061 reported by
Didier Roche-Tolomelli
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| content-hub (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| location-service (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| media-hub (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| u1db (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| ubuntu-download-manager (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| ubuntu-ui-toolkit (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
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.
Revision history for this message
| Zsombor Egri (zsombi) wrote | #1 |
| Changed in ubuntu-ui-toolkit (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
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.