We have moved to a new Sailfish OS Forum. Please start new discussions there.
29

Jolla Ghost Ship: Poor Communication Continues [subjective]

asked 2016-03-11 08:57:18 +0300

Moo-Crumpus gravatar image

updated 2016-03-13 17:06:39 +0300

January, 19:

Taalojärvi enters into early access We hope you enjoy the early access version of this release! We will release this to everybody *in a few weeks.

Again, after the poor communication during the "tablet crisis", vague promises are not kept. How long are two [misstyping: meant "few"] weeks? People ask for security patches. Whats up, jolla, are you still working?

edit retag flag offensive reopen delete

The question has been closed for the following reason "too subjective and argumentative" by Moo-Crumpus
close date 2016-03-13 15:36:10.821193

Comments

8

they only now are hiring back developers. Of course everything will take longer. I guess they will be back on track with monthly updates by summer (i hope)

virgi26 ( 2016-03-11 10:54:37 +0300 )edit
6

They were never on track with monthly updates. (OK, I joined the caravan a bit later so I may have missed a few monthly updates in the first 6 months or so, but ever since I have had a Jolla, the average frequency of updates was between 2 and 3 months. Including early updates.)

Either way, if you know you are under-staffed and cannot keep the promises, then simply do not give them.

Edit: You see the topic "last updated by pichlo". That's because I fixed a spelling mistake in the title.

pichlo ( 2016-03-11 13:13:46 +0300 )edit
9

@pichlo, i think the problem is that people take vague timeframes as cast iron promises.

r0kk3rz ( 2016-03-11 15:40:51 +0300 )edit
7

I don't agree. When someone talks of a few weeks, I take this seriously. It makes a difference whether spoken by a few days, weeks or months. So a few weeks are less than a month, otherwise one could call a month.A few weeks is less then a few month, in any case. I think the problem lies in Jolla's frivolous, thoughtless utterances. They hire developpers, said virgi26. Was there any communication about it, or is ist just a hopefull guess of him/her? Either way, if under-staffed simply don't give promisses, or be sincere.

When I have not enough employees to fix a bug, should I release alpha or beta early updates? NOT AT ALL.

Moo-Crumpus ( 2016-03-11 15:57:07 +0300 )edit
2

@r0kk3rz i dont think people take the timeframes too serious... its just that people are alway wondering whats going on... the discovery of the bug and that its the reson for the delay is several weeks old. so is it really that... jsut a weekly update would be enough. like:

this bug still blocks the release - updated timeframe: xxxxx

just spread information about whats going on inside - communication thats still whats wrong...

misc11 ( 2016-03-11 15:59:55 +0300 )edit
3

Open development would mean an open bugtracking tool so we can see and help with what is going on. Of course that would mean opensource in the first place.

lispy ( 2016-03-11 17:38:20 +0300 )edit
2

@chemist "There is no news, stay tuned!" every couple of days <- is that really what you are asking for?" No. I am asking for professionalism.

Moo-Crumpus ( 2016-03-11 21:35:11 +0300 )edit
8

It's simply never okay for you people. If they stay silent, it's "there is no communication, you suck". If they make extremely vague deadlines, it's "don't make empty promises, you suck". I bet if they set a specific date and released the revision before that date because it was already finished, you would complain about that as well.

nthn ( 2016-03-11 22:26:20 +0300 )edit

2 Answers

Sort by » oldest newest most voted
25

answered 2016-03-11 18:14:46 +0300

atlochowski gravatar image

@ossi1967 They still trying to solve this bug. They had delay because of MWC. Now I'm testing their solution for this bug and it looks it's working.

edit flag offensive delete publish link more

Comments

4

great!! something moves by jolla. happy :-)

cemoi71 ( 2016-03-11 21:51:07 +0300 )edit
14

answered 2016-03-11 09:12:19 +0300

ossi1967 gravatar image

Jolla said the public release is postponed because of this bug:

https://together.jolla.com/question/128005/bug201taalojarvi-auto-ignoring-incoming-connection/

(Btw: How come you translate "in a few weeks" to "two weeks"? ;) )

edit flag offensive delete publish link more

Comments

5

Releasing for each CVE one update isn't hard.

If one CVE fix is a blocker, then at least release the other fixes instead of postponing them all to never.

Updates should be split in security bugfixes and nice-to-have updates.

RoestVrijStaal ( 2016-03-11 09:24:48 +0300 )edit
6

Jolla mentioned it in post ... which number is ist? What is that blog for, then? Oh, if this is the new way to spread information, is there a tag of official jolla statements or am i informed by accidentally reading some postings or not. By the way, how come you still have a section for tablets on jolla.com? "Sorry, the tablet is sold out, but leave a mesasge to be informed about availabilty?" Pardon, this is ridiculous.

Moo-Crumpus ( 2016-03-11 10:10:57 +0300 )edit

@Moo-Crumpus The tablet is sold out, isn't it? What's wrong with that?

ossi1967 ( 2016-03-11 10:37:16 +0300 )edit

Yeah, but this bug is marked as (In release) for a few weeks now, doesn't that means it's been tackled down?

Sthocs ( 2016-03-11 12:45:02 +0300 )edit

good remark from atlochowski generally every business-shows take a lots of resources... especially before, but after too.
@atlochowski your comment direct above, is for me the best answer for this thread.

cemoi71 ( 2016-03-11 19:52:10 +0300 )edit

Question tools

Follow
3 followers

Stats

Asked: 2016-03-11 08:57:18 +0300

Seen: 2,676 times

Last updated: Mar 13 '16