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

Suggestion: develop (more) agile

asked 2014-01-25 13:24:12 +0300

hardcodes.de gravatar image

updated 2014-01-28 21:57:10 +0300

eric gravatar image

Could you please make some kind of agile development (in the sense of being agile not so much in religiously following some obscure procedures) and make updates available more frequently?

There is quite some backlog of things to do when I look around here and it would be very nice if fixed bugs would be rolled out as fast as possible. I mean this in opposite to wait for a big update that fixes more than one bug in one step. Of course there are some bugs that need a deep and wide investigation of why and how but there are some others that seem to be easy to fix (e.g. all those that are "just" makeup in the UI).

You know, change one button and roll that thing out, maybe to some beta volunteers if you hesitate somehow. The faster you roll out, the faster you get feedback.

edit retag flag offensive close delete



But the faster you roll out, the faster you get possible bricked devices. They still need time to make sure that the device doesn't need to be wiped two times a week because an broken update broke the pulley menu or something and it can't be fixed without factory reset

Bulder ( 2014-01-25 18:45:34 +0300 )edit

Rolling out fast does not mean to get careless and forget to test thoroughly. It's only done when it's done, but when it's ready: roll out - in contrast to collect many bug fixes and features in one big release.

hardcodes.de ( 2014-01-25 18:50:26 +0300 )edit

I think regular updates in an agile schedule (3 to 5 weeks) would really help SailFish to mature more rapidly.

StaticNoiseLog ( 2014-01-25 20:39:41 +0300 )edit

I didn't say and I don't want to say that the people at Jolla are doing a bad job. Regarding the low resources available smaller and even faster updates would not only help the users, they would help Jolla at the end: just look how many bugs are reported again and again = eating up resources.

hardcodes.de ( 2014-01-26 12:33:46 +0300 )edit

To make that clear: I believe the people at Jolla work hard! But there is a reason that questions like this arise: https://together.jolla.com/question/19316/please-clarify-is-jolla-working-on-questions-tagged-with-bug-although-they-are-not-tagged-with-roadmap/

hardcodes.de ( 2014-01-26 12:39:35 +0300 )edit

2 Answers

Sort by » oldest newest most voted

answered 2014-01-25 20:34:47 +0300

updated 2014-01-25 20:35:33 +0300

Monthly updates are said to be the target:


edit flag offensive delete publish link more

answered 2014-01-25 22:14:58 +0300

foss4ever gravatar image

updated 2014-01-25 22:21:59 +0300

From the original quarterly system update cycle to a montly is abt as 'agile' as anyone could have hoped for. Which other mobile OS vendor and device manufacturer releases system upgrades this frequently? Actually, only one similar case comes to my mind; the N9/MeeGo received three hugre PR-versions in the very short lifetime of the platform and device ;) So, no wonder sailors are now doing exactly that, releasing patches, bug fixes and new features, in my opinion, as rapidly as possible to reach feature-completeness the soonest. Maybe, if the pace was any quicker the packaking and the distribution of the upgrade would take proportionally too much time compared to the actual development.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools



Asked: 2014-01-25 13:24:12 +0300

Seen: 409 times

Last updated: Jan 25 '14