I don't think he's saying that to anyone directly. I think what he means is that the more people disseminate the information on how to get incomplete release candidates the more likely someone who doesn't quite understand what they are doing and what to expect installs one, trips over a bug, and then kicks up a fuss that their phone is broken.
At that point, Jolla will be more likely to lock down this public channel, and developers like coderus who take pride in delivering updated patches / software simultaneously with the release of an opt-in update won't be able to do that any more, and we all lose out.
Well. Here is one developer who opted-in, but despite that NEVER get any notifications in any other way.
And yes, the update is faulty!
While one devices updates without issues, my other device always fail if it is not factory reset first.
Just a friendly reminder: the only thing you can achieve by posting this information to public is not publishing release candidates to servers before making them available to opt-in program.
Don't they have the opt-in program _exactly_ for this?
At that point, Jolla will be more likely to lock down this public channel, and developers like coderus who take pride in delivering updated patches / software simultaneously with the release of an opt-in update won't be able to do that any more, and we all lose out.
Ahh.. now I get it. So we need a new opt-in to the existing opt-in program... er.. wait a second.
I don't think he's saying that to anyone directly. I think what he means is that the more people disseminate the information on how to get incomplete release candidates the more likely someone who doesn't quite understand what they are doing and what to expect installs one, trips over a bug, and then kicks up a fuss that their phone is broken.
At that point, Jolla will be more likely to lock down this public channel, and developers like coderus who take pride in delivering updated patches / software simultaneously with the release of an opt-in update won't be able to do that any more, and we all lose out.
On other hand it may help some people to learn and understand system better. I think most people learned linux that way, by testing and trying, and yes by making mistakes and fresh reinstall. Let's compare it to not official ppa's or beta releases for Ubuntu, some people can lock those and tell people to use only official repos as they might break system. But as we see information is public for everyone and its what makes community stronger with testers, people trying and learning on mistakes, who can after help others. If you think devs need separate opt-ins you are welcome to ask jolla, but to hide from others and make private groups is just unfair. And i'm pretty sure people who know about those updates shared it with less tech educated people, so why some are worth to know and others are not? Or we in hype of invite only elitism?
I think it's bad enough that jolla has no public roadmap and mostly things are developed behind doors.
You may disagree with me, but the fact is that maemo had strong community, where a lot of noobs became great devs just because people shared info, helped each other and not told you to "sit back and wait till you windows finish the installation". We already see that a lot of those devs abounded ship, because of elitism, closeness and lack of info from Jolla, now you want to prevent new generation from learning. If so, than stop asking why people want everything ready and out of box working and whine, coz the reason is that you force them to. Give the man fish or teach him how to go fishing...
Multiple levels of opting in?
1 Core software / patch developers
2 Userspace app developers
3 Really enthusiastic enthusiasts with cavalier attitudes
4 Chilled out enthusiasts
5 The paranoid-but-nosey
6 Dave999
7 Public release
And I don't want to prevent anyone trying anything, it's just sometimes people post the steps to switch update sources without any disclaimer, and not everyone understands that it's not finalised software to the level of testing that might be expected, and then they're forced to become a fisherman to fix their phone, and not everyone wants to spend the day smelling of fish. Hmm this analogy might be breaking down...
i wonder what was broken, been using this update for a few days with no noticeable issues
Same here. Other than a few patches from Coderus not working or applying, I haven't found any issues. It feels very stable and smooth and performance has improved once again. On my dad's Jolla it's the same: no noticeable issues, all running very stable.
Of course, there will always be exceptions. But for me and my dad, this 1.1.4 is running great so far for a few days now
1. Jolla leaked it via there official servers?
2. It's Available on the Web?
I might have missed something But why can't jolla just stop Rollin out the update? and limit their own mistake?
1. Not leaked, published. And, rolled out accidentially, causing half-updates for poor pple who did pkcon update in terminal.
2 Its available by 'hack' (=force version update)
And, I take my words back around coderus
This update can most likely break many things
Eespecially, but not limited to, if you use certain apps from warehouse, possibly even just by having warehouse installed.
This observation comes from installing it on my two devices.
1. will always break, and wont repair unless factory reset, after which it can update.
2. second device updated flawlessly - it never had the touch of any warehouse or openrepos stuff from there.
While I do think all should have the optione, I also strongly discourage new and inexperienced users to even think about this 'hack' update.
