ubuntu-phone team mailing list archive

[Alberto Mardegan <alberto.mardegan@xxxxxxxxxxxxx>]

Hi Zsombor,

On 20/05/2016 08:33, Zsombor Egri wrote:
[...]
> Second, frameworks do guard you from API breaks, indeed. What I am
> surprised a bit is you guys immediately thought this change will be an
> API break. Which is not. Again, this wasn't clear from the original
> mail.
[...]

You yourself wrote this just a couple of messages above:

"apps made prior to 15.04.5 (or wherever this change will land) will
stop working with pages using old header configuration setup. So if you
have apps in the store which uses APL with old page header
configurations, please update those."

Whether this is an API break or behavioural break or anything else, what
ultimately matters to developers is: does my app require changes?
I still haven't understood the answer to that (call me "slow" :-) ).

[...]
> Third: we do not have the labs module, therefore we are releasing
> components straight to the final module. But, we never said that 1.3 is
> feature complete, frozen. We said the API is released, and we stick to
> it, but as long as it is not frozen, we may and most probably will
> change behavior as the planned feature set requires us to do that. Once
> the component set gets frozen, we will open the next version and will
> work on that.
[...]

Unless I misunderstood you again, this is a terrible way of delivering
an SDK.
Developers must be told: the current stable release is X.Y. The stable
release can receive only bugfixes, which in no way can break the API or
cause behavioural changes (other than the matter of the bugfix, of course).
If UITK 1.3 does not satisfy these requirements, developers must be told
to use 1.2, and all the documentation and QtCreator templates must be
changed to recommend using 1.2.

Once an app has been published to the store it should always continue
working unmodified, until the framework is retired.

Ciao,
  Alberto