SailfishOS Update11 discussions - Page 12 - maemo.org

szopin | # 111 | 2015-02-03, 20:39 | Report

wow, the update-not-yet-here thread dropped out of last active threads
here is some fuel for discussion:
http://talk.maemo.org/showthread.php...31#post1459431
contrary to what it states anyone can opt-in, there are no developer checks

The Following 3 Users Say Thank You to szopin For This Useful Post:
Dave999, juiceme, mariusmssj

mariusmssj | # 112 | 2015-02-03, 21:08 | Report

Originally Posted by szopin View Post

wow, the update-not-yet-here thread dropped out of last active threads
here is some fuel for discussion:
http://talk.maemo.org/showthread.php...31#post1459431
contrary to what it states anyone can opt-in, there are no developer checks

Great step in the right direction!!!

Dave999 | # 113 | 2015-02-03, 21:19 | Report

Oh. And here I thought sailfish was dead. Good to see this thread come to life.

I want this update last, even after the mainstream...fully functional with copy&paste, arrow in keyboard and a utility and simplicity when editing forms that would make the most hard-core apple fanboy impressed. Intact. I will probably not even update until sail 2.0!

Opt-out for now.

Last edited by Dave999; 2015-02-03 at 21:36.

The Following User Says Thank You to Dave999 For This Useful Post:
juiceme

minimos | # 114 | 2015-02-04, 06:46 | Report

Originally Posted by szopin View Post

wow, the update-not-yet-here thread dropped out of last active threads
here is some fuel for discussion:
http://talk.maemo.org/showthread.php...31#post1459431
contrary to what it states anyone can opt-in, there are no developer checks

The important assumption is that you *feel* to be like a developer, and accept the risk that your device may break after a RC upgrade.

The Following User Says Thank You to minimos For This Useful Post:
juiceme

coderus | # 115 | 2015-02-04, 06:50 | Report

Originally Posted by minimos View Post

The important assumption is that you *feel* to be like a developer, and accept the risk that your device may break after a RC upgrade.

If you read announce carefully you can notice following:

Originally Posted by Details about the early access update in short

Early access releases should be considered "stable". Issues found during that period will either be fixed, or added to "known issues" on the release notes

The Following User Says Thank You to coderus For This Useful Post:
juiceme

Dave999 | # 116 | 2015-02-04, 07:35 | Report

So then...Jolla will need to:
1. Add the checkbox functionality.
2. Fix their update 11
3. Push it to the Opt-in
4. Handle the issues
5. Release the official update 11

We won't see that official update in a loooooonnnngggg time

mikelima | # 117 | 2015-02-04, 09:40 | Report

Originally Posted by Dave999 View Post

So then...Jolla will need to:
1. Add the checkbox functionality.
2. Fix their update 11
3. Push it to the Opt-in
4. Handle the issues
5. Release the official update 11

We won't see that official update in a loooooonnnngggg time

I do not think so. There is an option to mention the problem in the release notes, and if the problem is minor enough, that is the right choice to make.

Everytime you fix a bug you have the chance to introduce another one, so many times it is better to chose the known problem instead of the unknown one.

Some fixes may still happen, for fixes that seem innocuous enough.

And of course there is the possibility the early adopters find a blocker, and in this case you would be right, the release will be put on hold.

The Following 3 Users Say Thank You to mikelima For This Useful Post:
juiceme, mattaustin, zamorph

minimos | # 118 | 2015-02-04, 10:33 | Report

Originally Posted by coderus View Post

If you read announce carefully you can notice following: ...

Well, if you read carefully the text when you accept the opt-in, it also says this (bold enhancement is mine):

Originally Posted by

The early releases are mainly intended for developers, and the screening of potential critical issues with new releases before publishing to the wider audience. Please make sure you backup your data (as you always should) before installing the early release, as we cannot with certainty say that you will not have any problems (such as data loss or corruption). Note that opting in to the early release program does not void your warranty.

coderus | # 119 | 2015-02-04, 10:38 | Report

Originally Posted by minimos View Post

Well, if you read carefully the text when you accept the opt-in, it also says this (bold enhancement is mine):

somebody should startle you for sure

Dave999 | # 120 | 2015-02-04, 11:04 | Report

Originally Posted by mikelima View Post

I do not think so. There is an option to mention the problem in the release notes, and if the problem is minor enough, that is the right choice to make.

Everytime you fix a bug you have the chance to introduce another one, so many times it is better to chose the known problem instead of the unknown one.

Some fixes may still happen, for fixes that seem innocuous enough.

And of course there is the possibility the early adopters find a blocker, and in this case you would be right, the release will be put on hold.

Handle the issue doesn't mean fix. But even administrate, recreate, evaluation could take time. Nothing to worry about. Administration takes time and taking help from end-users with tasting is great. However it doesn't speed up the process but possibly the quality.

The Following User Says Thank You to Dave999 For This Useful Post:
Jordi