Revision history [back]

Hello Sailors,

after the last release and heavy discussion.

I open now a discussion about the strategy of release of software.
I don't want to put oil on fire, whether criticize negatively what the dev team and manager has done.

But remarks and critique (positive) should be done.
It gives me the possibility to explain my misunderstanding about the jolla-man release-in-charge strategy.

If i remember by last releases was some functionalities as not release versions, but beta or alpha brought inside.
I think about (pretty fast i admit it) vpn-tunnel, and shortly emoji-keyboard...

A release For me, is a part is enough well tested, that all bug and unintended reactions put aside.
Means all the "collection of functionality" have a stable stand and are as "release" noticed, with a release version.
A beta & alpha could not be arranged inside. If the need is to put inside, then all the functionality should be reduced to its stable form.
Otherwise, then push it on the software-market as beta/alpha.

for an os release version, wording like beta and alpha are not adapted.
If already reduced to a stable, but hasn't the full functions (like i suspect for the emoji keyboard).
Then it could be taken as release, with v1, with a mention that later comes further functions.

Thus that was my short point of you of a release strategy, with my misunderstanding on the one of the sfos. A little bit missy. but that's start point for having other point of view from other.
i'll be glad if it could help to give a constructive direction to the development of the os.

Have a good sail

Hello Sailors,

after the last release and heavy discussion.

I open now a discussion about the strategy of release of software.
I don't want to put oil on fire, whether criticize negatively what the dev team and manager has done.

But remarks and critique (positive) should be done.
It gives me the possibility to explain my misunderstanding about the jolla-man release-in-charge strategy.

If i remember by last releases was some functionalities as not release versions, but beta or alpha brought inside.
I think about (pretty fast i admit it) vpn-tunnel, and shortly emoji-keyboard...

A release For me, is a part is enough well tested, that all bug and unintended reactions put aside.
Means all the "collection of functionality" have a stable stand and are as "release" noticed, with a release version.
A beta & alpha could not be arranged inside. If the need is to put inside, then all the functionality should be reduced to its stable form.
Otherwise, then push it on the software-market as beta/alpha.

for an os release version, wording like beta and alpha are not adapted.
If already reduced to a stable, but hasn't the full functions (like i suspect for the emoji keyboard).
Then it could be taken as release, with v1, with a mention that later comes further functions.

Thus that was my short point of you of a release strategy, with my misunderstanding on the one of the sfos. A little bit missy. but that's start point for having other point of view from other.
i'll be glad if it could help to give a constructive direction to the development of the os.

Have a good sail