Originally Posted by coderus (Post 1444178)

much quick, so news!

Originally Posted by aQUICK1 (Post 1444179)

OLd news and small update!:p

Originally Posted by juiceme (Post 1444220)

Might be small update but I asolutely love it!
See, I just noticed this fixes one of the most annoying bugs in the device, which leaves only the browser-mis-hitting-link bug out there!!

After 1.1.0.39 conman fix my WLAN does not disconnet any longer :D
I can happily leave WLAN on for hours, and when I ssh to the device it is reachable!
Even after I went out for a run for 30 minutes with my device, when I came back it automatically connected to my WLAN and is still connected :eek:

I'm so happy! :)

Originally Posted by juiceme (Post 1444220)

Might be small update but I asolutely love it!

Originally Posted by Dave999 (Post 1444030)

Will this be released to all in Oct?

Originally Posted by Dave999 (Post 1444030)

Anyone know what process jolla using for dev. Qa. Builds. Release?

Originally Posted by w00t (Post 1444399)

I'd doubt it. Read on for why.



Development internally focuses on an "always green" master (relatively speaking. Sometimes it breaks, but that's hopefully rare, knock on wood.) In practice, this means that internal development builds are basically always reflecting the master state of git repositories around the place. Developers mostly run this.

At some point during the development cycle, things are branched off to create a release (because, well, you need to settle down and make things sane and have some control over what is going to be released). QA happens on this level, and release candidates (internally) happen off this at a regular rate.

Once things are deemed good enough (no known blockers open), then things get pushed out for public release.

In practice, this means that there can be multiple release tracks ongoing at a time. For instance, while one update is maturing for release, the next is already generally cooking in the development tree.