Hi all,
I have collected our thoughts about this topic on a form of a blog post:
https://developer.ubuntu.com/en/blog/2016/05/24/about-versioning-ubuntu-ui-toolkit/
One extra point what I wish to mention is that we do scan and analyze
those applications in the store to have visibility on how our APIs are used.
But most importantly I really would like to emphasize that the term
"stable API" does not mean that the "implementation of the API is frozen".
Also, referring to the very topic of this thread. Both the APL and the
Page APIs are stable and safe to use. Just because we gave a heads up
that these two components will not blend in the future. To give you the
stupidest analogy of the year... football teams are cool, and sport
cars are cool too. But do not expect a football team to fit in to a
sportcar. Even if you kind of thought that they do fit in, or even if we
gave the false impression that they do. API stability is one thing...
what you can do with a component is an other.
cheers,
bzoltan
On 23/05/16 10:17, Alberto Mardegan wrote:
Hi Zsombor,
I'll just focus on the essential issue and try to get to a
constructive suggestion:
On 21/05/2016 23:18, Zsombor Egri wrote:
No, it wouldn't. Because once we open 1.4, people will jump on it,
because some features they need will be available only in 1.4, and in
case we have to drop some support like now in one of the components, we
will have this conversation again, and again, and again...
That's the core of the problem: you must make all efforts so that people
don't start using development versions *without knowing that they are
under development* (emphasis on the essential part).
At least for the core apps, it certainly makes sense to use the very
latest development version of the toolkit, and breakages are not an
issue: all of these developers are either paid or anyway happy to work
on improving these apps, and having to update them to follow the UITK
developments is not a problem.
However, you must have a clear contract with third party developers,
where you tell them which versions of the toolkit are considered stable,
and never touch them in a way that could break any apps.
Then, developers who want to use the latest features can use the
unstable version, but then it must be a conscious decision and not
happen accidentally.
So, regardless of the versioning scheme you choose, my recommendation is:
1) emit a qWarning() when one imports the development version of the
toolkit;
2) fix developer.ubuntu.com, because now it's telling everyone to use
1.3, without any warnings of potential issues.
Ciao,
Alberto
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp
