Revisiting: updates release schedule

asked 2014-10-14 16:17:16 +0300

dsilveira
7805 ●77 ●110 ●101

updated 2014-12-02 15:03:06 +0300

Given the recent update 9/10 release issue, I believe it's time to revisit the question of updates release cycle.

I believe that if Jolla in the spirit of openness, followed the open mantra of release early, release often, they could have a git branch for each small fix, tracking the current stable, and as soon as each one becomes stable itself, get it out the door, and update the stable with that patch, cascading to the follower branches.

This way, we instead of waiting a long time for a big release (which by having several fixes and improvements, has an increased complexity), and trying to hit a monthly date, and missing, we would have regular small and simple updates, improving the phone step by step, and always getting an updated phone, unlike...

EDIT: It's been 2 months, and still no official update 9, let alone update 10. My network is still terribly unstable! This question should seriously be considered!

edit retag flag offensive close delete

Comments

You think just like me! I agree your post This way should be better for have minor bugs and issues; and make ours Sailfish more stable

michdeskunk ( 2014-10-14 17:30:49 +0300 )edit

Sounds simple, you are just forgetting all the dependencies, many of those small fixes would require full testing rounds of the entire OS, quite big resources are needed to do several of those in short period of time.

VDVsx ( 2014-10-16 17:23:36 +0300 )edit

have you heard of continuos integration services? Automated testing?

dsilveira ( 2014-10-17 15:50:19 +0300 )edit

I think everyone could understand that some updates might take longer. What is annoying is that they block the release of a lot of other smaller ones, like most of the top voted questions on TJC regarding interface improvements (on lipstick and Jolla apps). I think what I'm suggesting is reasonable, and probably even needed to keep users happy and feeling appreciated!

dsilveira ( 2014-10-17 15:54:04 +0300 )edit

Yes, those look great on paper but not always work as 'advertised', not counting the amount of work and resources needed to automate many uses cases. If things were so simple why big companies take so long to release SW updates for their devices ? I'm pretty sure they have a 'few more' resources than Jolla :)

VDVsx ( 2014-10-17 16:07:21 +0300 )edit

answered 2014-12-02 15:26:44 +0300

lupastro

4100 ●57 ●76 ●76

Even though I am someway the same opinion than you, I have to say that it is not that easy. Each software update/change requires a lot of testing. Including regression testing to check that everything that has not been touched is still working. Regression Testing is very time consuming.

I think that instead of having 3 Updates (+ its corresponding testing times), it's much more optimal to have one single bigger update.

I have worked a long time testing software and hardware in a major communication company, and I can assure you that there's nothing worse than regression testing. Yes, I am also disappointed with the delays and I am not trying to justify them, but I know how these things are since I have experienced them.

Comments

+1 thanks for this great and informative comment!!!

peter-berlin ( 2014-12-02 17:00:43 +0300 )edit

I understand it's hard, but surely there's a way to improve automation of it, to do continuous integration.

where there's a will, there's a way!

dsilveira ( 2014-12-02 19:04:52 +0300 )edit

Revisiting: updates release schedule

Comments

1 Answer

Comments

Question tools

Stats

Related questions

Revisiting: updates release schedule

Comments

1 Answer

Comments

Question tools

Public thread

Stats

Related questions