ubuntu-phone team mailing list archive

[Zoltán Balogh <zoltan.balogh@xxxxxxxxxxxxx>]

Hi,

Sorry folks, I owe you a little correction:

We have just released the official framework to 15.04.1  So if you want 
to opt to the UITK 1.3 you do not need to set -dev but to 15.04.1 in the 
mainifest file

Also the UITK API deprecation in 1.3 version is possible only for those 
APIs that were made available after the last framework release. So 1.3 
APIs made available before the 15.04.1 framework can only be deprecated 
only in a higher version of the UITK.

Sorry again for missing these out from the mail.

cheers,

Zoltan



On 10/09/2015 04:39 PM, Zoltán Balogh wrote:
> Hi,
>
> After following and participating to several discussions about the 
> $SUBJECT I though that it is good idea to clarify few things :)
>
> The roadmap [1] of the UITK development is still valid. So the focus 
> right now is the 1.3 version what is all about convergence and 
> performance. The 1.3 version of the UITK was opened for development 
> and published in May and so app developers can use it since then.
>
> It means that on a device updated since 19th of May the 1.3 UITK is 
> available and any app binded to a -dev framework can use it.
>
> So what stability promise the 1.3 UITK comes?
>
> First of all, let's clarify the terminology:
>
> Released / Stable - APIs never extended, never deprecated. Simple 
> untouchable (0.1, 1.0, 1.1, 1.2)
>
> Unreleased / Unstable - APIs are continuously extended, new 
> properties, components come with every new revision. APIs are changed 
> and deprecated super rarely and with special process. (1.3)
>
> The process of deprecating an API  ->
>
> 1. We announce the upcoming change,
> 2. UITK and so the application starts to give warnings
> 3. In the following release the API is deprecated
>
> It means that stable APIs we never break or deprecate in a scope of a 
> single release of the UITK. I mean it :) _NEVER_
>
> For example we have introduced the ToolBar components in 1.1, marked 
> as soon to be deprecated in 1.2 and deprecated in 1.3.
>
> Of course new APIs introduced in 1.3 might get deprecated in 1.3, but 
> that is also very unlikely to happen and if happens then it will be 
> properly communicated.
>
> cheers,
>
> bzoltan
>
> [1] 
> https://developer.ubuntu.com/en/blog/2015/04/15/retrospective-and-roadmap-ui-toolkit/