I think this bodes terribly for Jolla and the development of Sailfish generally. It gives a glimpse into how haphazard, lackadaisical or generally disorganised or directionless Jolla are, and is completely consistent with much of the rest of their activity (or lack thereof).

The near 6 months between stable updates, because they thought it would be a good idea to implement a new version of Qt without any infrastructure in place to roll things back or forward, or branch development, suggests pretty staggering naivety.

Their communication is generally extremely poor. Only now, 14 months after launch, are we beginning to get very vague 'roadmap' type statements.

Various simple things don't get fixed or hotfixed. Some of them which are allowed to go for months and months. One suspects the reason is "can't be bothered" more than anything.

The most amazing thing to me is that all we know about paid for apps is in April last year they were aiming for an H2 launch, and in early December it was a "priority" but being held up by "technical issues". Clearly they missed their extremely vague H2 window, and what technical issues exactly? There are numerous off the shelf solutions that they could probably implement within days. Are we to believe that they're flailing around trying to code their own secure payments system from the ground up? If so, why? If so, why are they not implementing an off the shelf product as an interim solution? Sailfish has lost enough developers already, none of which it could afford to lose, and given both the tiny size of the ecosystem and the total lack of incentive to develop for it, how will it ever become self sufficient? What if Warehouse / OpenRepos hadn't taken off? Sailfish would be completely dead.

It seems like Jolla have yet to contact Zeta about this. It's pretty saddening and makes it extremely hard to have any optimism about the way the company is run.